CVE-2025-37930
Last modified
CVE-2025-37930 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.6, < 5.10.238 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.182 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.138 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.90 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.28 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.6 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-37930?
How severe is CVE-2025-37930?
How do I fix CVE-2025-37930?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-37925In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37926In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37927In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37928In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37929In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3793The Buddypress Force Password Change plugin for WordPress is…4.2
- CVE-2025-37931In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37932In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37933In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37934In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-37935In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37936In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-37930?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST