CVE-2025-68223 Details
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)
A deadlock vulnerability has been identified in the Linux kernel's handling of fence signaling within the Radeon Direct Rendering Manager (DRM) module. This issue arises because the fence lock can be in an unknown state when the signaling operation is performed. In the Radeon implementation, this lock also serves as the wait queue lock, leading to a self-deadlock scenario. The problem occurs when the signaling function attempts to advance the wait queue, a step that is unnecessary and can cause a deadlock. The vulnerability has been addressed by removing the redundant queue progression, allowing the signaling function to safely return a false value when appropriate.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for downloading the patched version are available on the official Linux kernel website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/73bc12d6a547f9571ce4393acfd73c004e2df9e5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7e3e9b3a44c23c8eac86a41308c05077d6d30f41 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9d0ed508a9e2af82951ce7d834f58c139fc2bd9b | kernel.org | Patch |
| https://git.kernel.org/stable/c/9eb00b5f5697bd56baa3222c7a1426fa15bacfb5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d40a72d7e3bad4dfb311ef078f5a57362f088c7f | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.18, < 6.1.162 >= 6.2, < 6.6.123 >= 6.7, < 6.12.60 >= 6.13, < 6.17.10 6.18 rc1 6.18 rc2 6.18 rc3 6.18 rc4 6.18 rc5 6.18 rc6 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 26, 2026 | Initial Analysis | [email protected] |
| Feb 6, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | New CVE Received | kernel.org |