CVE-2025-39737None▾ SunlitIn 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 5.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < 9f1f4e95031f84867c5821540466d62f88dab8caLinux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < 1ef72a7fedc5bca70e8cc980985790de10d407aaLinux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < a04de4c40aab9b338dfa989cf4aec70fd187eeb2Linux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < f014c10d190b92aad366e56b445daffcd1c075e4Linux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29bLinux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < 8d2d22a55ffe35c38e69795468a7addd1a80e9ceLinux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < 926092268efdf1ed7b55cf486356c74a9e7710d1Linux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < 9b80430c194e4a114dc663c1025d56b4f3d0153dLinux >= 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 < d1534ae23c2b6be350c8ab060803fbf6e9682adcLinux 5.4Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses