drm/amdgpu: reject oversized IBs with per-ring packet limits (CVE-2026-80576) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80576

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

Answer in brief

CVE-2026-80576 records a Unknown severity vulnerability in drm/amdgpu: reject oversized IBs with per-ring packet limits. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 26, 2026Updated Aug 26, 2026Source checked Aug 26, 2026First seen by HOL Aug 26, 2026Material review Aug 26, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e164ba1057175fb8a370d8e05cbff5c57eac0c8 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1474f3970d1afd303e12ff14d06808eabb371576 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <07fe270ec07c138a70afe7a81e115a85c35c545c \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd37f9dd5b5ab70a46fa7bc76623c0528d602b27 \|\| >=0 <6.12.105 \|\| >=0 <6.18.46 \|\| >=0 <7.1.10	6e164ba1057175fb8a370d8e05cbff5c57eac0c8, 1474f3970d1afd303e12ff14d06808eabb371576, 07fe270ec07c138a70afe7a81e115a85c35c545c, fd37f9dd5b5ab70a46fa7bc76623c0528d602b27, 6.12.105, 6.18.46, 7.1.10

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to 6e164ba1057175fb8a370d8e05cbff5c57eac0c8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 26, 2026

Sources and claim methodology

Upstream source 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)

Quoted source text, attributed separately from HOL analysis.