CVE-2026-23295
Deadlock Vulnerability in Linux accel/amdxdna During Suspend/Resume
Publication date: 2026-03-25
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | * |
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's amdxdna acceleration component. When an application issues a query IOCTL while the system is in auto suspend mode, a deadlock can happen. Specifically, the query path holds a device lock (dev_lock) and then calls a function to resume the device (pm_runtime_resume_and_get()), which waits for the suspend operation to finish. Meanwhile, the suspend callback tries to acquire the same device lock, causing both processes to block each other and resulting in a deadlock.
The fix involves releasing the device lock before calling the resume function and reacquiring it afterward, as well as acquiring the device lock in the resume callback to maintain consistent locking.
How can this vulnerability impact me? :
This vulnerability can cause the system to deadlock during suspend and resume operations when certain queries are issued. This deadlock can lead to system hangs or freezes, potentially requiring a reboot and causing disruption of services or loss of data.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by updating the Linux kernel to a version where the deadlock issue in accel/amdxdna during suspend and resume is resolved.
Specifically, the fix involves releasing dev_lock before calling pm_runtime_resume_and_get() and reacquiring it after the call completes, as well as acquiring dev_lock in the resume callback to maintain consistent locking.
Therefore, the immediate mitigation step is to apply the kernel update that includes this fix.