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

> A local attacker can cause system instability or denial of service by submitting oversized command buffers to the AMD GPU driver due to missing size validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-97845, BELL-CVE-2026-80576, DEBIAN-CVE-2026-80576, GHSA-mv2f-pcc7-qh27, UBUNTU-CVE-2026-80576

## What is CVE-2026-80576?

CVE-2026-80576 is a high-severity vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2026-80576?


## How do I fix CVE-2026-80576?

Apply the vendor's patch.

## Is CVE-2026-80576 being exploited?

There is no known exploitation of CVE-2026-80576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80576 and fix it if it is affected.

What it is: CVE-2026-80576 is a high-severity vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80576 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80576/ (Markdown: https://insights.sbomify.com/CVE-2026-80576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80576
- OSV: https://osv.dev/vulnerability/CVE-2026-80576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80576/
Summaries are generated and may contain mistakes; the official description above is the record.