CVE-2025-39737

published 11 Sep 2025 · updated 7 Nov 2026

mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1ef72a7fedc5bca70e8cc980985790de10d407aa, Kernel 5.15.190, Kernel 6.1.149 and 14 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <1ef72a7fedc5bca70e8cc980985790de10d407aa, >=5.11 <5.15.190, >=5.16 <6.1.149, >=5.4.1 <5.4.297, >=5.5 <5.10.241, >=6.13 <6.15.11, >=6.16 <6.16.2, >=6.2 <6.6.103, >=6.7 <6.12.43, =5.4, =6.17, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <f014c10d190b92aad366e56b445daffcd1c075e4, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29b, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <d1534ae23c2b6be350c8ab060803fbf6e9682adc, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <a04de4c40aab9b338dfa989cf4aec70fd187eeb2, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <9f1f4e95031f84867c5821540466d62f88dab8ca, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <9b80430c194e4a114dc663c1025d56b4f3d0153d, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <926092268efdf1ed7b55cf486356c74a9e7710d1, >=2abd839aa7e615f2bbc50c8ba7deb9e40d186768 <8d2d22a55ffe35c38e69795468a7addd1a80e9ce1ef72a7fedc5bca70e8cc980985790de10d407aa, 5.15.190, 6.1.149, 5.4.297, 5.10.241, 6.15.11, 6.16.2, 6.6.103, 6.12.43, f014c10d190b92aad366e56b445daffcd1c075e4, e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29b, d1534ae23c2b6be350c8ab060803fbf6e9682adc, a04de4c40aab9b338dfa989cf4aec70fd187eeb2, 9f1f4e95031f84867c5821540466d62f88dab8ca, 9b80430c194e4a114dc663c1025d56b4f3d0153d, 926092268efdf1ed7b55cf486356c74a9e7710d1, 8d2d22a55ffe35c38e69795468a7addd1a80e9ce
debiandebian_linux=11.0
linux-kernel: Kernel>=6.7.0 <6.12.43, >=6.2.0 <6.6.103, >=6.16.0 <6.16.2, >=6.13.0 <6.15.11, >=5.5.0 <5.10.241, >=5.4.0 <5.4.297, >=5.16.0 <6.1.149, >=5.11.0 <5.15.1906.12.43, 6.6.103, 6.16.2, 6.15.11, 5.10.241, 5.4.297, 6.1.149, 5.15.190

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-39737 severity on Zeptric[![CVE-2025-39737](https://zeptric.io/badge/cve/CVE-2025-39737.svg)](https://zeptric.io/cve/CVE-2025-39737)