CVE-2026-74454

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size

vc4_overflow_mem_work() points BPOA at a 512KB slot inside the 16MB binner BO, but writes the size of the whole BO to BPOS. On every binner out-of-memory event the PTB is therefore authorized to write tile lists across all the other slots (which may hold the tile state, tile alloc and overflow memory of in-flight jobs) and, for any slot but the first, past the end of the binner BO into unrelated CMA memory.

Since CMA pages are recycled into page cache and user allocations, this is arbitrary memory corruption by GPU DMA. In practice it shows up as GPU hangs with corrupted control list pointers, userspace heap corruption, a GPU that stays permanently wedged after the first hang, and occasional full system crashes, whenever a job overflows the initial binner slot.

The bug dates back to the conversion from a dedicated overflow BO (where writing the full BO size was correct) to the slotted binner BO.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6395789e4739aa5177bbec0fa0f07ccc38d249b0
generic

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f2291a119e9a8b696ae8bb36e86b75d272ceaea
generic

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e33ca7f44be64beed2735bb76b86eb65ba8c05b
generic

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0badb30871004d34df87be33e853536f0b69885f

Vendor Advisories for CVE-2026-74454(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 30× in last 7d / 30× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 17:24 UTCGHSA enrichment
  3. 2026-08-20 05:31 UTCGHSA enrichment
  4. 2026-08-19 17:37 UTCEG score recompute
  5. 2026-08-19 17:37 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:46 UTCEG score recompute
  8. 2026-08-19 16:46 UTCGHSA enrichment
  9. 2026-08-19 06:39 UTCGHSA enrichment
  10. 2026-08-18 18:43 UTCEG score recompute
  11. 2026-08-18 18:43 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:49 UTCGHSA enrichment
  15. 2026-08-17 18:55 UTCEG score recompute
  16. 2026-08-17 18:55 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:25 UTCEG score recompute
  19. 2026-08-17 06:25 UTCGHSA enrichment
  20. 2026-08-17 05:55 UTCEG score recompute 7.80
  21. 2026-08-17 05:55 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-08-17 05:25 UTCEG score recompute
  24. 2026-08-17 05:25 UTCGHSA enrichment
  25. 2026-08-17 05:24 UTCMITRE cvelistV5
Show 5 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-15 13:27 UTCNVD update
  4. 2026-08-15 12:41 UTCEG score recompute
  5. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74454?
CVE-2026-74454 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size vc4overflowmem_work() points BPOA at a 512KB slot inside the 16MB binner BO, but writes the size of the whole BO to BPOS. On every binner out-of-memory event…
When was CVE-2026-74454 disclosed?
CVE-2026-74454 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74454 actively exploited?
CVE-2026-74454 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74454?
CVE-2026-74454 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74454, 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-74454

Explore →

Is Your Infrastructure Affected by CVE-2026-74454?

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