The kernel pre‑patch code allowed 64‑bit user fence writes to be accepted by JPEG v2.0 command submission rings. This defect could allow an attacker with sufficient privileges or the ability to inject kernel‑level code to manipulate fence values in a way that bypasses kernel safeguards, potentially corrupting memory or executing arbitrary code within the kernel context. As the effect involves kernel memory and critical data structures, the risk of a direct privilege escalation or denial‑of‑service scenario is elevated. The vulnerability is characterized as a CWE‑1287 weakness where critical kernel structures are improperly protected from user input.

The issue is present in the Linux kernel in the DRM/amdgpu JPEG subsystem. All kernel releases that include the AMGPU JPEG v2.0 ring without the patch are vulnerable. The patch identified in the commit graph is part of the overall Linux kernel, so any distribution shipping a kernel that does not incorporate commit 96179da0c6b059eb31706a0abe8dd6381c533143 is affected, regardless of the distribution version. System administrators should verify whether the running kernel comes from a distribution that has backported this fix or whether they must manually update to a newer kernel that contains it.

The CVSS score of 7.8 indicates a high severity potential, but the EPSS score of less than 1% suggests a low probability of exploitation at present. The vulnerability is not listed in CISA’s KEV catalog. An attacker would need to execute code at kernel privilege to influence and exploit the JPEG ring’s fence handling, implying local or privileged user access. Once a patch is in place, this attack vector is removed, since the kernel will reject any command submissions that contain 64‑bit fences for the JPEG v2.0 ring.