The flaw resides in the AMD XDNA graphics driver of the Linux kernel. During a buffer‑object synchronization ioctl, the driver looks up the handle in the caller’s drm_file but, for device‑direct debug operations, it mistakenly uses the caller’s client pointer when invoking the lower‑level sync routine. Because the client pointer is tied to the buffer object’s persisted state rather than the ioctl’s context, this mismatch can corrupt the hardware‑context structures maintained in an xarray and allow a local attacker to read or write privileged kernel memory. The description explicitly states that this misuse can lead to improper memory accesses and potential privilege escalation. Based on the description, it is inferred that the attacker must be able to open the DRM device node, and the likely attack vector is a crafted ioctl call that triggers this sync operation.

All systems running a Linux kernel derived from mainline Linux kernel source are affected. The CNA identifiers list "Linux:Linux," indicating that any distribution kernel that has not yet incorporated the commits 216e43d93dd49 and 7caf2a2351d405 is vulnerable. No specific version range is documented, so administrators should treat every kernel release prior to the patch as vulnerable until the fixes are applied.

The CVE is not listed in the CISA KEV catalog and its CVSS score is 7.8, indicating a moderate to high severity. The EPSS score is < 1%, indicating a very low probability of exploitation. However, the vulnerability is a local‑only flaw that can be triggered by an unprivileged user with access to a DRM device node. A successful exploitation would corrupt kernel data structures and can grant root privileges on the host. Based on the description, it is inferred that exploitation requires local access to the DRM device node and that the likely attack vector is a crafted ioctl request. Given the lack of mitigations and the severity of potential escalation, the risk warrants immediate attention.