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)
References6
- git.kernel.org/stable/c/07fe270ec07c138a70afe7a81e115a85c35c545c
- git.kernel.org/stable/c/1474f3970d1afd303e12ff14d06808eabb371576
- git.kernel.org/stable/c/67a5d905c17a5066b0f6f950da11da93d56d122b
- git.kernel.org/stable/c/6e164ba1057175fb8a370d8e05cbff5c57eac0c8
- git.kernel.org/stable/c/ecdaefe825555f133a2ef80f39d1ae94d6e1b26a
- git.kernel.org/stable/c/fd37f9dd5b5ab70a46fa7bc76623c0528d602b27
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 2 · as of 9 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.