CVE-2025-37930
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-617
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.238
- Linux Kernel < 5.15.182
- Linux Kernel < 6.1.138
- Linux Kernel < 6.6.90
- Linux Kernel < 6.12.28
- Linux Kernel < 6.14.6
- Linux Kernel 6.15
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37930.md and follow it. Check whether this project is affected by CVE-2025-37930. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0453825167ecc816ec15c736e52316f69db0deb9
- https://git.kernel.org/stable/c/126f5c6e0cb84e5c6f7a3a856d799d85668fb38e
- https://git.kernel.org/stable/c/2ec0f5f6d4768f292c8406ed92fa699f184577e5
- https://git.kernel.org/stable/c/39d6e889c0b19a2c79e1c74c843ea7c2d0f99c28
- https://git.kernel.org/stable/c/47ca11836c35c5698088fd87f7fb4b0ffa217e17
- https://git.kernel.org/stable/c/b771b2017260ffc3a8d4e81266619649bffcb242
- https://git.kernel.org/stable/c/bbe5679f30d7690a9b6838a583b9690ea73fe0e9
References
- https://git.kernel.org/stable/c/0453825167ecc816ec15c736e52316f69db0deb9
- https://git.kernel.org/stable/c/126f5c6e0cb84e5c6f7a3a856d799d85668fb38e
- https://git.kernel.org/stable/c/2ec0f5f6d4768f292c8406ed92fa699f184577e5
- https://git.kernel.org/stable/c/39d6e889c0b19a2c79e1c74c843ea7c2d0f99c28
- https://git.kernel.org/stable/c/47ca11836c35c5698088fd87f7fb4b0ffa217e17
- https://git.kernel.org/stable/c/b771b2017260ffc3a8d4e81266619649bffcb242
- https://git.kernel.org/stable/c/bbe5679f30d7690a9b6838a583b9690ea73fe0e9
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html