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

> A race condition in the Radeon DRM driver causes a self-deadlock when checking fence status, leading to system denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-72425, AZL-78401, BELL-CVE-2025-68223, DEBIAN-CVE-2025-68223, GHSA-qv7h-6r58-hcx8, ROOT-OS-DEBIAN-11-CVE-2025-68223, ROOT-OS-DEBIAN-12-CVE-2025-68223, ROOT-OS-DEBIAN-13-CVE-2025-68223, ROOT-OS-UBUNTU-2204-CVE-2025-68223, ROOT-OS-UBUNTU-2404-CVE-2025-68223, UBUNTU-CVE-2025-68223

## What is CVE-2025-68223?

CVE-2025-68223 is a medium-severity vulnerability in Linux kernel, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-68223?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-68223?

Apply the vendor's patch.

## Is CVE-2025-68223 being exploited?

There is no known exploitation of CVE-2025-68223 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68223 and fix it if it is affected.

What it is: CVE-2025-68223 is a medium-severity vulnerability in Linux kernel, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68223 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68223/ (Markdown: https://insights.sbomify.com/CVE-2025-68223/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68223
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68223
- OSV: https://osv.dev/vulnerability/CVE-2025-68223

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68223/
Summaries are generated and may contain mistakes; the official description above is the record.