CVE-2025-37930 [Medium] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.10%	0.17%	+0.07%
2	2026-03-16	0.02%	0.10%	+0.08%
3	2025-11-11	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.10%

0.17%

+0.07%

2026-03-16

0.02%

0.10%

+0.08%

2025-11-11

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2025-37930

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2025-37930 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6.	https://security-tracker.debian.org/tracker/CVE-2025-37930
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2025-37930
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2025-37930/
`ubuntu`	medium	CVE-2025-37930 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 168, ignored 164, not-affected 68, needed 3, needs-triage 2, pending 1.	https://ubuntu.com/security/CVE-2025-37930

Affected software / configurations for CVE-2025-37930

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.6, < 5.10.238	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.182	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.1.138	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.2, < 6.6.90	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.7, < 6.12.28	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.14.6	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc1::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc2::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc3::::::
linux	linux_kernel	6.15	cpe:2.3:o:linux:linux_kernel:6.15:rc4::::::
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2025-37930

URL	Tags
https://git.kernel.org/stable/c/0453825167ecc816ec15c736e52316f69db0deb9	Patch
https://git.kernel.org/stable/c/126f5c6e0cb84e5c6f7a3a856d799d85668fb38e	Patch
https://git.kernel.org/stable/c/2ec0f5f6d4768f292c8406ed92fa699f184577e5	Patch
https://git.kernel.org/stable/c/39d6e889c0b19a2c79e1c74c843ea7c2d0f99c28	Patch
https://git.kernel.org/stable/c/47ca11836c35c5698088fd87f7fb4b0ffa217e17	Patch
https://git.kernel.org/stable/c/b771b2017260ffc3a8d4e81266619649bffcb242	Patch
https://git.kernel.org/stable/c/bbe5679f30d7690a9b6838a583b9690ea73fe0e9	Patch
https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html	Mailing List Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html	Mailing List Third Party Advisory

URL

CVE-2025-37930 | drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()

Exploit prediction scoring system (EPSS) score for CVE-2025-37930

Common vulnerability scoring system (CVSS) metrics for CVE-2025-37930

Weakness enumeration for CVE-2025-37930

OS Trackers for CVE-2025-37930

Affected software / configurations for CVE-2025-37930

References for CVE-2025-37930