Skip to main content
VulnerabilityPublished

CVE-2026-99647: Linux kernel · mm/huge_memory: split huge PUDs when adjusting VMA boundaries

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99647· Medium

Not known to be exploited · fixed in bd918ee291da2d76dd03b5f9c2c2e550095ab538 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in bd918ee291da2d76dd03b5f9c2c2e550095ab538, 4636bc02303032f20710d97f40adb8f4eed22a66, 605ebb555bc8695b309dcd462be6c1437ef98421 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to bd918ee291da2d76dd03b5f9c2c2e550095ab538, 4636bc02303032f20710d97f40adb8f4eed22a66, 605ebb555bc8695b309dcd462be6c1437ef98421 or 23e570927421d569fdc510d5f3f29542a43eeda5.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101, < bd918ee291da2d76dd03b5f9c2c2e550095ab538
Fixed in
  • bd918ee291da2d76dd03b5f9c2c2e550095ab538
LinuxLinuxAffected
  • ≥ f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101, < 4636bc02303032f20710d97f40adb8f4eed22a66
Fixed in
  • 4636bc02303032f20710d97f40adb8f4eed22a66
LinuxLinuxAffected
  • ≥ f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101, < 605ebb555bc8695b309dcd462be6c1437ef98421
Fixed in
  • 605ebb555bc8695b309dcd462be6c1437ef98421
LinuxLinuxAffected
  • ≥ f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101, < 23e570927421d569fdc510d5f3f29542a43eeda5
Fixed in
  • 23e570927421d569fdc510d5f3f29542a43eeda5
LinuxLinuxAffected
  • =6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: split huge PUDs when adjusting VMA boundaries PFN mappings such as VFIO PCI BAR mappings can use PUD leaves while allowing VMA splits at page granularity. However, vma_adjust_trans_huge() only handles PMDs. After faulting a writable PUD-sized VFIO BAR mapping, changing its first page to read-only with mprotect() makes the PMD walk treat the PUD leaf as a PMD table. Applying MADV_DONTFORK to the first PMD-sized chunk leaves the PUD spanning two VMAs: the PMD-aligned boundary skips splitting. Walk the page tables once at each adjusted boundary and split a huge PUD or PMD leaf as needed. Handle PUD leaves even when the boundary is PMD-aligned.

References

Community reviews

Loading reviews…