CVE-2025-68223 | drm/radeon: delete radeon_fence_process in is_signaled, no deadlock

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)

Published: 2025-12-16 Last update: 2026-02-26 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-68223 is rated Low Risk (23.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-68223

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-17 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-68223

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-68223

OS Trackers for CVE-2025-68223

vendor priority summary link
debian not yet assigned CVE-2025-68223 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1. https://security-tracker.debian.org/tracker/CVE-2025-68223
redhat medium — https://access.redhat.com/security/cve/CVE-2025-68223
suse medium CVE-2025-68223 severity moderate: SUSE including 375 source package names (13.2-9.1:libsystemd0-254.23-1.1, 13.2-9.1:libudev1-254.23-1.1, …), 697 product×package rows across 99 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (99 product lines)): Fixed 425, Known Affected 231, First Fixed 25, Known Not Affected 16. https://www.suse.com/security/cve/CVE-2025-68223/
ubuntu medium CVE-2025-68223 medium priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1405 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1010, ignored 182, released 129, needed 82, pending 2. https://ubuntu.com/security/CVE-2025-68223

Affected software / configurations for CVE-2025-68223

Vendor Product Version Raw CPE
linux linux_kernel >= 3.18, < 6.1.162 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.123 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.60 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.17.10 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc1:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc2:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:*
linux linux_kernel 6.18 cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:*

References for CVE-2025-68223

cvelogic Threat Intelligence