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-38084mm/hugetlb: unshare page tables during VMA split, not before

Description

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: unshare page tables during VMA split, not before Currently, __split_vma() triggers hugetlb page table unsharing through vm_ops->may_split(). This happens before the VMA lock and rmap locks are taken - which is too early, it allows racing VMA-locked page faults in our process and racing rmap walks from other processes to cause page tables to be shared again before we actually perform the split. Fix it by explicitly calling into the hugetlb unshare logic from __split_vma() in the same place where THP splitting also happens. At that point, both the VMA and the rmap(s) are write-locked. An annoying detail is that we can now call into the helper hugetlb_unshare_pmds() from two different locking contexts: 1. from hugetlb_split(), holding: - mmap lock (exclusively) - VMA lock - file rmap lock (exclusively) 2. hugetlb_unshare_all_pmds(), which I think is designed to be able to call us with only the mmap lock held (in shared mode), but currently only runs while holding mmap lock (exclusively) and VMA lock Backporting note: This commit fixes a racy protection that was introduced in commit b30c14cd6102 ("hugetlb: unshare some PMDs when splitting VMAs"); that commit claimed to fix an issue introduced in 5.13, but it should actually also go all the way back. [[email protected]: v2]

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 16 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-38084, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.22% · top 88% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < e8847d18cd9fff1edbb45e963d9141273c3b539c
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < 366298f2b04d2bf1f2f2b7078405bdf9df9bd5d0
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < 2511ac64bc1617ca716d3ba8464e481a647c1902
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < af6cfcd0efb7f051af221c418ec8b37a10211947
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < 9cf5b2a3b72c23fb7b84736d5d19ee6ea718762b
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < 8a21d5584826f4880f45bbf8f72375f4e6c0ff2a
    • affected 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa – < 081056dc00a27bccb55ccc3c6f230a3d5fd3f7e0
  • Linux · Linux

    • affected 2.6.20
    • unaffected < 2.6.20
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.95 – ≤ 6.6.*
    • unaffected 6.12.35 – ≤ 6.12.*
    • unaffected 6.15.4 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .