Security Resilience

CVE-2025-37802

Linux Kernel ≤ 6.12.26

Published
08 May 2025
Modified
14 September 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0036 28th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-37802 is a high-severity Improper Locking (CWE-667) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING" wait_event_timeout() will set the state of the current task to TASK_UNINTERRUPTIBLE, before doing the condition check. This means that ksmbd_durable_scavenger_alive()…

more

will try to acquire the mutex while already in a sleeping state. The scheduler warns us by giving the following warning: do not call blocking ops when !TASK_RUNNING; state=2 set at [<0000000061515a6f>] prepare_to_wait_event+0x9f/0x6c0 WARNING: CPU: 2 PID: 4147 at kernel/sched/core.c:10099 __might_sleep+0x12f/0x160 mutex lock is not needed in ksmbd_durable_scavenger_alive().

CWE(s)
CWE-667

Related Threats

CVEs Like This One

CVE-2024-47736Same product: Linux Linux Kernel
CVE-2026-43029Same product: Linux Linux Kernel
CVE-2025-21851Same product: Linux Linux Kernel
CVE-2024-42090Same product: Linux Linux Kernel
CVE-2024-50044Same product: Linux Linux Kernel
CVE-2024-26873Same product: Linux Linux Kernel
CVE-2024-35990Same product: Linux Linux Kernel
CVE-2024-48876Same product: Linux Linux Kernel
CVE-2025-21767Same product: Linux Linux Kernel
CVE-2024-26962Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.15 · ≤ 6.12.26 · 6.13 — 6.14.5

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect race conditions and locking errors before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit missing or incorrect lock usage.

A.8.32 Change management partial match
blocks

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-667, a class-level weakness, and none of its children carries one either.

References