CVE-2026-80576

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

HIGH
8.8
CVSS Score
Published: August 26, 2026 at 02:37 PM UTC
Updated: October 21, 2026 at 01:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2d38ceaf99ed015f2a0b9af3499791bd3a3daae21
Vendor states this is fixed in 07fe270ec07c138a70afe7a81e115a85c35c545c (fixed)
Vendor states this is fixed in 1474f3970d1afd303e12ff14d06808eabb371576 (fixed)
Vendor states this is fixed in 6e164ba1057175fb8a370d8e05cbff5c57eac0c8 (fixed)
Vendor states this is fixed in fd37f9dd5b5ab70a46fa7bc76623c0528d602b27 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card