CVE-2025-68223
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2026-02-26

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: delete radeon_fence_process in is_signaled, no deadlock Delete the attempt to progress the queue when checking if fence is signaled. This avoids deadlock. dma-fence_ops::signaled can be called with the fence lock in unknown state. For radeon, the fence lock is also the wait queue lock. This can cause a self deadlock when signaled() tries to make forward progress on the wait queue. But advancing the queue is unneeded because incorrectly returning false from signaled() is perfectly acceptable. (cherry picked from commit 527ba26e50ec2ca2be9c7c82f3ad42998a75d0db)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2026-02-26
Generated
2026-05-07
AI Q&A
2025-12-16
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 10 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.2 (inc) to 6.6.123 (exc)
linux linux_kernel 6.18
linux linux_kernel 6.18
linux linux_kernel 6.18
linux linux_kernel 6.18
linux linux_kernel 6.18
linux linux_kernel 6.18
linux linux_kernel From 3.18 (inc) to 6.1.162 (exc)
linux linux_kernel From 6.13 (inc) to 6.17.10 (exc)
linux linux_kernel From 6.7 (inc) to 6.12.60 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-667 The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's Radeon DRM driver involves a deadlock issue caused by the function is_signaled attempting to progress the queue while checking if a fence is signaled. The problem arises because dma-fence_ops::signaled can be called with the fence lock in an unknown state, and for Radeon, this lock is also the wait queue lock. This can cause a self deadlock when signaled() tries to advance the wait queue unnecessarily. The fix deletes the attempt to progress the queue in is_signaled, avoiding the deadlock since incorrectly returning false from signaled() is acceptable.


How can this vulnerability impact me? :

This vulnerability can cause a deadlock in the Linux kernel's Radeon DRM driver, potentially leading to system hangs or freezes when the fence signaling mechanism is used. This can impact system stability and availability, especially in environments relying on Radeon graphics hardware and the affected kernel versions.


What immediate steps should I take to mitigate this vulnerability?

Apply the updated Linux kernel patch that deletes the radeon_fence_process in is_signaled to avoid the deadlock issue. This fix prevents the self deadlock by not attempting to progress the queue when checking if the fence is signaled. Updating to the fixed kernel version is the recommended mitigation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart