CVE-2025-68223: Linux kernel · drm/radeon: delete radeon_fence_process in is_signaled, no deadlock
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d40a72d7e3bad4dfb311ef078f5a57362f088c7f : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in d40a72d7e3bad4dfb311ef078f5a57362f088c7f, 73bc12d6a547f9571ce4393acfd73c004e2df9e5, 9eb00b5f5697bd56baa3222c7a1426fa15bacfb5 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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)
References
- git.kernel.org/stable/c/d40a72d7e3bad4dfb311ef078f5a57362f088c7f (opens in a new tab)
- git.kernel.org/stable/c/9d0ed508a9e2af82951ce7d834f58c139fc2bd9b (opens in a new tab)
- git.kernel.org/stable/c/73bc12d6a547f9571ce4393acfd73c004e2df9e5 (opens in a new tab)
- git.kernel.org/stable/c/7e3e9b3a44c23c8eac86a41308c05077d6d30f41 (opens in a new tab)
- git.kernel.org/stable/c/9eb00b5f5697bd56baa3222c7a1426fa15bacfb5 (opens in a new tab)