GPU hang via Radeon fence self-deadlock
Published Dec 16, 2025 · Updated Dec 16, 2025
Improper locking in the Linux kernel Radeon DRM driver allows local users to hang GPU work by triggering fence signaling. The radeon_fence_signaled callback calls radeon_fence_process while the fence lock may already be held; because that lock also guards the wait queue, the callback can acquire it recursively and self-deadlock. Exploitation requires local low-privileged access and an active Radeon driver, and the resulting deadlock interrupts graphics work.
Summary
What happened
Improper locking in the Linux kernel Radeon DRM driver allows local users to hang GPU work by triggering fence signaling. The radeon_fence_signaled callback calls radeon_fence_process while the fence lock may already be held; because that lock also guards the wait queue, the callback can acquire it recursively and self-deadlock. Exploitation requires local low-privileged access and an active Radeon driver, and the resulting deadlock interrupts graphics work.
The record
- CVE
- CVE-2025-68223
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <73bc12d6a547f9571ce4393acfd73c004e2df9e5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7e3e9b3a44c23c8eac86a41308c05077d6d30f41
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo