Answer in brief
CVE-2025-37802 records a Unknown severity vulnerability in ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING". The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0626e6641f6b467447c81dd7678a69c66f7746cf <8f805b3746d2f41702c77cba22f94f8415fadd1a || >=0626e6641f6b467447c81dd7678a69c66f7746cf <cd161198e091e8a62b9bd631be970ea9a87d2d6a || >=0626e6641f6b467447c81dd7678a69c66f7746cf <1df0d4c616138784e033ad337961b6e1a6bcd999 | 8f805b3746d2f41702c77cba22f94f8415fadd1a, cd161198e091e8a62b9bd631be970ea9a87d2d6a, 1df0d4c616138784e033ad337961b6e1a6bcd999 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37802 records a Unknown severity vulnerability in ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING". The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0626e6641f6b467447c81dd7678a69c66f7746cf <8f805b3746d2f41702c77cba22f94f8415fadd1a || >=0626e6641f6b467447c81dd7678a69c66f7746cf <cd161198e091e8a62b9bd631be970ea9a87d2d6a || >=0626e6641f6b467447c81dd7678a69c66f7746cf <1df0d4c616138784e033ad337961b6e1a6bcd999 | 8f805b3746d2f41702c77cba22f94f8415fadd1a, cd161198e091e8a62b9bd631be970ea9a87d2d6a, 1df0d4c616138784e033ad337961b6e1a6bcd999 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
May 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.