CVE-2025-37930: Linux kernel · drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1088.95~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1088.95~20.04.1, 5.15.0-1094.103~20.04.1, 5.15.0-1087.96~20.04.2 +59
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7649-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7650-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7655-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7649-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7665-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7665-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7686-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2025-37930 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-37930 (opens in a new tab)
- git.kernel.org/linus/bbe5679f30d7690a9b6838a583b9690ea73fe0e9 (opens in a new tab)
- git.kernel.org/stable/c/0453825167ecc816ec15c736e52316f69db0deb9 (opens in a new tab)
- git.kernel.org/stable/c/126f5c6e0cb84e5c6f7a3a856d799d85668fb38e (opens in a new tab)
- git.kernel.org/stable/c/2ec0f5f6d4768f292c8406ed92fa699f184577e5 (opens in a new tab)
- git.kernel.org/stable/c/47ca11836c35c5698088fd87f7fb4b0ffa217e17 (opens in a new tab)
- git.kernel.org/stable/c/b771b2017260ffc3a8d4e81266619649bffcb242 (opens in a new tab)
- git.kernel.org/stable/c/bbe5679f30d7690a9b6838a583b9690ea73fe0e9 (opens in a new tab)
- ubuntu.com/security/notices/USN-7649-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7650-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7655-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7649-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7665-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7665-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7654-5 (opens in a new tab)