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-38681mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd()

Description

In the Linux kernel, the following vulnerability has been resolved: mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() Memory hot remove unmaps and tears down various kernel page table regions as required. The ptdump code can race with concurrent modifications of the kernel page tables. When leaf entries are modified concurrently, the dump code may log stale or inconsistent information for a VA range, but this is otherwise not harmful. But when intermediate levels of kernel page table are freed, the dump code will continue to use memory that has been freed and potentially reallocated for another purpose. In such cases, the ptdump code may dereference bogus addresses, leading to a number of potential problems. To avoid the above mentioned race condition, platforms such as arm64, riscv and s390 take memory hotplug lock, while dumping kernel page table via the sysfs interface /sys/kernel/debug/kernel_page_tables. Similar race condition exists while checking for pages that might have been marked W+X via /sys/kernel/debug/kernel_page_tables/check_wx_pages which in turn calls ptdump_check_wx(). Instead of solving this race condition again, let's just move the memory hotplug lock inside generic ptdump_check_wx() which will benefit both the scenarios. Drop get_online_mems() and put_online_mems() combination from all existing platform ptdump code paths.

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-38681, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (18 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 4.7.

Affected products

  • Linux · Linux

    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < 3ee9a8c27bfd72c3f465004fa8455785d61be5e8
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < 69bea84b06b5e779627e7afdbf4b60a7d231c76f
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < ac25ec5fa2bf6e606dc7954488e4dded272fa9cd
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < 1636b5e9c3543b87d673e32a47e7c18698882425
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < ff40839e018b82c4d756d035f34a63aa2d93be83
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < 67995d4244694928ce701928e530b5b4adeb17b4
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < ca8c414499f2e5337a95a76be0d21b728ee31c6b
    • affected bbd6ec605c0fc286c3f8ce60b4ed44635361d58b – < 59305202c67fea50378dcad0cc199dbc13a0e99a
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • 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

References13

Sources

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

Badge for a README or a ticket

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

Record last updated .