Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39737mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39737, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < 9f1f4e95031f84867c5821540466d62f88dab8ca
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < 1ef72a7fedc5bca70e8cc980985790de10d407aa
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < a04de4c40aab9b338dfa989cf4aec70fd187eeb2
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < f014c10d190b92aad366e56b445daffcd1c075e4
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29b
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < 8d2d22a55ffe35c38e69795468a7addd1a80e9ce
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < 926092268efdf1ed7b55cf486356c74a9e7710d1
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < 9b80430c194e4a114dc663c1025d56b4f3d0153d
    • affected 2abd839aa7e615f2bbc50c8ba7deb9e40d186768 – < d1534ae23c2b6be350c8ab060803fbf6e9682adc
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39737 badge
[![CVE-2025-39737](https://cveledger.app/badge/CVE-2025-39737.svg)](https://cveledger.app/cve/CVE-2025-39737)

Record last updated .