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-37930drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()

Description

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill() Nouveau is mostly designed in a way that it's expected that fences only ever get signaled through nouveau_fence_signal(). However, in at least one other place, nouveau_fence_done(), can signal fences, too. If that happens (race) a signaled fence remains in the pending list for a while, until it gets removed by nouveau_fence_update(). Should nouveau_fence_context_kill() run in the meantime, this would be a bug because the function would attempt to set an error code on an already signaled fence. Have nouveau_fence_context_kill() check for a fence being signaled.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 12 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-37930, 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.23% · top 86% of all CVEs (18 Nov 2026)
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 ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < 39d6e889c0b19a2c79e1c74c843ea7c2d0f99c28
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < 2ec0f5f6d4768f292c8406ed92fa699f184577e5
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < 47ca11836c35c5698088fd87f7fb4b0ffa217e17
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < 126f5c6e0cb84e5c6f7a3a856d799d85668fb38e
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < b771b2017260ffc3a8d4e81266619649bffcb242
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < 0453825167ecc816ec15c736e52316f69db0deb9
    • affected ea13e5abf807ea912ce84eef6a1946b9a38c6508 – < bbe5679f30d7690a9b6838a583b9690ea73fe0e9
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.182 – ≤ 5.15.*
    • unaffected 6.1.138 – ≤ 6.1.*
    • unaffected 6.6.90 – ≤ 6.6.*
    • unaffected 6.12.28 – ≤ 6.12.*
    • unaffected 6.14.6 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .