Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80576drm/amdgpu: reject oversized IBs with per-ring packet limits

Description

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)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80576, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < ecdaefe825555f133a2ef80f39d1ae94d6e1b26a
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 67a5d905c17a5066b0f6f950da11da93d56d122b
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 6e164ba1057175fb8a370d8e05cbff5c57eac0c8
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 1474f3970d1afd303e12ff14d06808eabb371576
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 07fe270ec07c138a70afe7a81e115a85c35c545c
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < fd37f9dd5b5ab70a46fa7bc76623c0528d602b27
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80576 badge
[![CVE-2026-80576](https://cveledger.app/badge/CVE-2026-80576.svg)](https://cveledger.app/cve/CVE-2026-80576)

Record last updated .