CVE-2026-80576

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.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: 8.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/amdgpu: reject oversized IBs with per-ring packet limits

On GFX rings, amdgpu_cs_p2_ib() passed user-supplied ib_bytes through to ib->length_dw without a limit, while ring_emit_ib() encodes length into packet fields. Oversized values can corrupt adjacent control bits and destabilize command submission.

Add a per-ring IB packet size limit helper and reject command submissions exceeding the corresponding dword limit before IB allocation. Use the documented 20-bit limit for GFX/compute/SDMA/VPE, and apply the MM fallback limit for other ring types.

(cherry picked from commit 7f48fa2cf62e3fa6c9c3870aa74988f773247e52)

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

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (4)

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

drm/amdgpu: reject oversized IBs with per-ring packet limits - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: reject oversized IBs with per-ring packet limits - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07fe270ec07c138a70afe7a81e115a85c35c545c
generic

drm/amdgpu: reject oversized IBs with per-ring packet limits - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1474f3970d1afd303e12ff14d06808eabb371576
generic

drm/amdgpu: reject oversized IBs with per-ring packet limits - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e164ba1057175fb8a370d8e05cbff5c57eac0c8

Vendor Advisories for CVE-2026-80576(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 15× in last 7d / 15× 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-30 05:31 UTCGHSA enrichment
  2. 2026-08-29 17:41 UTCGHSA enrichment
  3. 2026-08-29 05:50 UTCEG score recompute
  4. 2026-08-29 05:49 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 17:59 UTCGHSA enrichment
  7. 2026-08-28 06:04 UTCGHSA enrichment
  8. 2026-08-27 18:11 UTCEG score recompute
  9. 2026-08-27 18:11 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 06:18 UTCEG score recompute▲ 8.80
  12. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  13. 2026-08-26 15:43 UTCNVD update
  14. 2026-08-26 14:42 UTCEG score recompute
  15. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80576?
CVE-2026-80576 is a high vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: reject oversized IBs with per-ring packet limits On GFX rings, amdgpucsp2ib() passed user-supplied ibbytes through to ib->lengthdw without a limit, while ringemit_ib() encodes length into packet fields. Oversized values…
When was CVE-2026-80576 disclosed?
CVE-2026-80576 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80576 actively exploited?
CVE-2026-80576 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-80576?
CVE-2026-80576 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-80576?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80576, 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-80576

Explore →

Is Your Infrastructure Affected by CVE-2026-80576?

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

Start Free Scan →Browse All CVEs