Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-68223, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 954605ca3f897ad617123279eb3404a404cce5ab – < d40a72d7e3bad4dfb311ef078f5a57362f088c7f
    • affected 954605ca3f897ad617123279eb3404a404cce5ab – < 9d0ed508a9e2af82951ce7d834f58c139fc2bd9b
    • affected 954605ca3f897ad617123279eb3404a404cce5ab – < 73bc12d6a547f9571ce4393acfd73c004e2df9e5
    • affected 954605ca3f897ad617123279eb3404a404cce5ab – < 7e3e9b3a44c23c8eac86a41308c05077d6d30f41
    • affected 954605ca3f897ad617123279eb3404a404cce5ab – < 9eb00b5f5697bd56baa3222c7a1426fa15bacfb5
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.123 – ≤ 6.6.*
    • unaffected 6.12.60 – ≤ 6.12.*
    • unaffected 6.17.10 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68223 badge
[![CVE-2025-68223](https://cveledger.app/badge/CVE-2025-68223.svg)](https://cveledger.app/cve/CVE-2025-68223)

Record last updated .