What is CVE-2025-37802?

CVE-2025-37802 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Improper Locking flaw (CWE-667), affecting Linux kernel versions from 5.15 onward and patched in 6.12.26, 6.14.5 and 6.15. CVE-2025-37802 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2025-37802?

CVE-2025-37802 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2025-37802?

Yes, CVE-2025-37802 has been patched. Fixed versions include 6.12.26, 6.14.5 and 6.15. If you are running Linux kernel 5.15 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2025-37802 actively exploited?

CVE-2025-37802 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2025-37802

Medium

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() 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().

Package Linux Kernel

Published 2025-05-08

Last modified 2025-06-05

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

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

Weakness type

CWE-667

CVE-2025-37802 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 5.15 and later are affected. Fixed in 6.12.26, 6.14.5, 6.15 and their respective stable series.

Affected from

≥ 5.15

Fixed in

✓ 6.12.26 6.12.x ✓ 6.14.5 6.14.x ✓ 6.15

References

3 total

Kernel Git
https://git.kernel.org/stable/c/1df0d4c616138784e033ad337961b6e1a6bcd999

Patch
Kernel Git
https://git.kernel.org/stable/c/8f805b3746d2f41702c77cba22f94f8415fadd1a

Patch
Kernel Git
https://git.kernel.org/stable/c/cd161198e091e8a62b9bd631be970ea9a87d2d6a

Patch

Details

CVE ID CVE-2025-37802

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2025-05-08

Modified 2025-06-05

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2025-37802?

CVE-2025-37802 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 5.15 onward and has been patched in 6.12.26, 6.14.5 and 6.15. CVE-2025-37802 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2025-37802?

CVE-2025-37802 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2025-37802?

Yes. CVE-2025-37802 has been patched. Fixed versions include 6.12.26, 6.14.5 and 6.15. If you are running Linux kernel 5.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2025-37802 actively exploited?

No. CVE-2025-37802 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.