Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-39737

medium

In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was obser…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134] The test system was running a workload with hot unplug happening in parallel. Then kemleak decided to disable itself due to its inability to allocate more kmemleak objects. The debug kernel has its CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000. The soft lockup happened in kmemleak_do_cleanup() when the existing kmemleak objects were being removed and deleted one-by-one in a loop via a workqueue. In this particular case, there are at least 40,000 objects that need to be processed and given the slowness of a debug kernel and the fact that a raw_spinlock has to be acquired and released in __delete_object(), it could take a while to properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-09-11 17:15
Modified: 2026-11-05 22:17
NVD status: Modified
Last synced 1 week ago
Verified against the source API 2026-11-05 22:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.4.1 <5.4.297, ≥5.5 <5.10.241, ≥5.11 <5.15.190, ≥5.16 <6.1.149, ≥6.2 <6.6.103, ≥6.7 <6.12.43
debian / debian_linux 11.0

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/1ef72a7fedc5bca70e8cc980985790de10d407aa
Patch / mitigation: https://git.kernel.org/stable/c/8d2d22a55ffe35c38e69795468a7addd1a80e9ce
Patch / mitigation: https://git.kernel.org/stable/c/926092268efdf1ed7b55cf486356c74a9e7710d1
Patch / mitigation: https://git.kernel.org/stable/c/9b80430c194e4a114dc663c1025d56b4f3d0153d
Patch / mitigation: https://git.kernel.org/stable/c/9f1f4e95031f84867c5821540466d62f88dab8ca
Patch / mitigation: https://git.kernel.org/stable/c/a04de4c40aab9b338dfa989cf4aec70fd187eeb2
Patch / mitigation: https://git.kernel.org/stable/c/d1534ae23c2b6be350c8ab060803fbf6e9682adc
Patch / mitigation: https://git.kernel.org/stable/c/e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29b
Patch / mitigation: https://git.kernel.org/stable/c/f014c10d190b92aad366e56b445daffcd1c075e4

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 22:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs