CVE-2026-72149

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: tegra: Fix burst size calculation

Currently, the Tegra GPC DMA hardware requires the transfer length to be a multiple of the max burst size configured for the channel. When a client requests a transfer where the length is not evenly divisible by the configured max burst size, the DMA hangs with partial burst at the end.

Fix this by reducing the burst size to the largest power-of-2 value that evenly divides the transfer length. For example, a 40-byte transfer with a 16-byte max burst will now use an 8-byte burst (40 / 8 = 5 complete bursts) instead of causing a hang.

This issue was observed with the PL011 UART driver where TX DMA transfers of arbitrary lengths were stuck.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a3b76b54e06d73166af4d1a284a0e0711889060c
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f0f5de1091119679d87f60dfb1acbff4b2a0ed3
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7926c1e4be86379945fb5f168888ac4d2aaf6c91
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/735951baa311c66353405dcac39375dd66441db0
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e37e9e230c7e848bd8e8cd4db15bb18bcf11ad1
generic

dmaengine: tegra: Fix burst size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4651df83b6c796daead3447e8fd874322918ee4f

Vendor Advisories for CVE-2026-72149(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:31 UTCEG score recompute
  2. 2026-08-21 05:31 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:49 UTCGHSA enrichment
  5. 2026-08-20 06:07 UTCGHSA enrichment
  6. 2026-08-19 18:25 UTCEG score recompute
  7. 2026-08-19 18:25 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:20 UTCGHSA enrichment
  10. 2026-08-18 18:30 UTCEG score recompute
  11. 2026-08-18 18:30 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:47 UTCGHSA enrichment
  15. 2026-08-17 19:01 UTCEG score recompute
  16. 2026-08-17 19:01 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:21 UTCEG score recompute
  19. 2026-08-17 06:21 UTCGHSA enrichment
  20. 2026-08-17 06:00 UTCEG score recompute▲ 7.50
  21. 2026-08-17 06:00 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  23. 2026-08-17 05:32 UTCEG score recompute
  24. 2026-08-17 05:32 UTCGHSA enrichment
  25. 2026-08-17 05:24 UTCMITRE cvelistV5
Show 7 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:42 UTCGHSA enrichment
  5. 2026-08-15 06:23 UTCNVD update
  6. 2026-08-15 06:11 UTCEG score recompute
  7. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72149?
CVE-2026-72149 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: dmaengine: tegra: Fix burst size calculation Currently, the Tegra GPC DMA hardware requires the transfer length to be a multiple of the max burst size configured for the channel. When a client requests a transfer where the length…
When was CVE-2026-72149 disclosed?
CVE-2026-72149 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72149 actively exploited?
CVE-2026-72149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72149?
CVE-2026-72149 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-72149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72149, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72149

Explore →

Is Your Infrastructure Affected by CVE-2026-72149?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs