Skip to main content
VulnerabilityPublished Updated

CVE-2025-68223: Linux kernel · drm/radeon: delete radeon_fence_process in is_signaled, no deadlock

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d40a72d7e3bad4dfb311ef078f5a57362f088c7f : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 954605ca3f897ad617123279eb3404a404cce5ab, < d40a72d7e3bad4dfb311ef078f5a57362f088c7f
Fixed in
  • d40a72d7e3bad4dfb311ef078f5a57362f088c7f
LinuxLinuxAffected
  • ≥ 954605ca3f897ad617123279eb3404a404cce5ab, < 73bc12d6a547f9571ce4393acfd73c004e2df9e5
Fixed in
  • 73bc12d6a547f9571ce4393acfd73c004e2df9e5
LinuxLinuxAffected
  • ≥ 954605ca3f897ad617123279eb3404a404cce5ab, < 9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
Fixed in
  • 9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
LinuxLinuxAffected
  • ≥ 954605ca3f897ad617123279eb3404a404cce5ab, < 9d0ed508a9e2af82951ce7d834f58c139fc2bd9b
Fixed in
  • 9d0ed508a9e2af82951ce7d834f58c139fc2bd9b
LinuxLinuxAffected
  • ≥ 954605ca3f897ad617123279eb3404a404cce5ab, < 7e3e9b3a44c23c8eac86a41308c05077d6d30f41
Fixed in
  • 7e3e9b3a44c23c8eac86a41308c05077d6d30f41
LinuxLinuxAffected
  • =3.18
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

Community reviews

Loading reviews…