# CVE-2025-37802: ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING"

> A race condition in the ksmbd module causes a kernel warning and potential instability when acquiring a mutex in an uninterruptible state.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2025
- **Updated:** 14 Sep 2026
- **Also known as:** BELL-CVE-2025-37802, DEBIAN-CVE-2025-37802, GHSA-56c5-8gc7-wj67, ROOT-OS-DEBIAN-12-CVE-2025-37802, ROOT-OS-UBUNTU-2204-CVE-2025-37802, ROOT-OS-UBUNTU-2404-CVE-2025-37802, UBUNTU-CVE-2025-37802

## What is CVE-2025-37802?

CVE-2025-37802 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2025-37802?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37802?

Apply the vendor's patch.

## Is CVE-2025-37802 being exploited?

There is no known exploitation of CVE-2025-37802 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37802 and fix it if it is affected.

What it is: CVE-2025-37802 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-37802 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-37802/ (Markdown: https://insights.sbomify.com/CVE-2025-37802/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-37802
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-37802
- OSV: https://osv.dev/vulnerability/CVE-2025-37802

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-37802/
Summaries are generated and may contain mistakes; the official description above is the record.