The report details a deadlock flaw in the AMD X‑DNA accelerator driver for the Linux kernel. When the driver’s runtime suspend callback drains the job workqueue before suspending the device, a running job that calls pm_runtime_resume_and_get() can re‑enter the suspend path. The two code paths can block each other, preventing the device from completing suspend or resume operations and potentially halting workloads that depend on the accelerator. The weakness is a concurrency defect described by CWE‑367. No code execution path is exposed, so the impact is limited to a local DoS on the affected device.

All Linux kernel releases that contain the AMD X‑DNA driver before inclusion of commit 6b13cb8f48a42ddf6dd98865b673a82e37ff238b are affected. That encompasses every kernel version shipped with the driver code prior to that commit, across all mainline distributions. The vulnerability applies only to systems with an AMD X‑DNA accelerator and the associated driver present.

EPSS data indicates a low probability of exploitation, with a score of less than 1%, and the vulnerability is not listed in CISA KEV, indicating no known active exploitation. The description implies that an attacker would need the ability to submit jobs to the device, which typically requires local or privileged access; this inference is not explicitly stated but follows from the need for job execution. Exploitation would therefore result in a denial of service for the device and any user workloads that rely on it, without providing remote code execution or data exfiltration capabilities.