Answer in brief
CVE-2025-39736 records a Medium severity (CVSS 5.5) vulnerability in mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. 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), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c5665868183fec689dbab9fb8505188b2c4f0757 <c7b6ea0ede687e7460e593c5ea478f50aa41682a || >=c5665868183fec689dbab9fb8505188b2c4f0757 <4b0151e1d468eb2667c37b7af99b3c075072d334 || >=c5665868183fec689dbab9fb8505188b2c4f0757 <f249d32bb54876b4b6c3ae071af8ddca77af390b || >=c5665868183fec689dbab9fb8505188b2c4f0757 <62879faa8efe8d8a9c7bf7606ee9c068012d7dac || >=c5665868183fec689dbab9fb8505188b2c4f0757 <1da95d3d4b7b1d380ebd87b71a61e7e6aed3265d || >=c5665868183fec689dbab9fb8505188b2c4f0757 <a0854de00ce2ee27edf39037e7836ad580eb3350 || >=c5665868183fec689dbab9fb8505188b2c4f0757 <08f70be5e406ce47c822f2dd11c1170ca259605b || >=c5665868183fec689dbab9fb8505188b2c4f0757 <a181b228b37a6a5625dad2bb4265bb7abb673e9f || >=c5665868183fec689dbab9fb8505188b2c4f0757 <47b0f6d8f0d2be4d311a49e13d2fd5f152f492b2 | c7b6ea0ede687e7460e593c5ea478f50aa41682a, 4b0151e1d468eb2667c37b7af99b3c075072d334, f249d32bb54876b4b6c3ae071af8ddca77af390b, 62879faa8efe8d8a9c7bf7606ee9c068012d7dac, 1da95d3d4b7b1d380ebd87b71a61e7e6aed3265d, a0854de00ce2ee27edf39037e7836ad580eb3350, 08f70be5e406ce47c822f2dd11c1170ca259605b, a181b228b37a6a5625dad2bb4265bb7abb673e9f, 47b0f6d8f0d2be4d311a49e13d2fd5f152f492b2 |
| Linux/Linuxgeneric | 5.4 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock When netpoll is enabled, calling pr_warn_once() while holding kmemleak_lock in mem_pool_alloc() can cause a deadlock due to lock inversion with the netconsole subsystem. This occurs because pr_warn_once() may trigger netpoll, which eventually leads to __alloc_skb() and back into kmemleak code, attempting to reacquire kmemleak_lock. This is the path for the deadlock. mem_pool_alloc() -> raw_spin_lock_irqsave(&kmemleak_lock, flags); -> pr_warn_once() -> netconsole subsystem -> netpoll -> __alloc_skb -> __create_object -> raw_spin_lock_irqsave(&kmemleak_lock, flags); Fix this by setting a flag and issuing the pr_warn_once() after kmemleak_lock is released.
Quoted source text, attributed separately from HOL analysis.