The vulnerability in the Linux kernel’s AMDGPU DRM driver allowed 64‑bit user fence writes to be accepted in JPEG control streams, even though the JPEG v4.0.5 ring does not support such fences. This regression could lead to incorrect handling of synchronization information and potential corruption of GPU resources, and it is an instance of CWE-229: improper restriction of operations within buffer bounds. The patch introduces a sentinel that marks the ring as lacking user‑fence support and rejects any control stream that contains user fences, effectively preventing the faulty processing that could destabilize the GPU subsystem.

All Linux distributions using the Linux kernel with the AMDGPU DRM driver and the JPEG v4.0.5 ring are affected. The issue applies to every kernel version prior to the commit that adds the no_user_fence check, regardless of distribution, as the vulnerability is present in the generic linux kernel code.

The CVSS score of 7.8 indicates a high severity level. The EPSS score of less than 1% shows that exploit traffic is currently minimal. Based on the description, the attack likely requires local access to the kernel’s GPU driver and the ability to craft a JPEG control stream containing a user fence. No remote exploitation or privilege escalation is described, so the vector appears to be local and non‑trivial. The vulnerability is not listed in the CISA KEV catalog, implying that widespread exploitation has not yet been observed. Nevertheless, the high CVSS and potential for a denial of service warrant prompt action.