Skip to main content
VulnerabilityPublished

CVE-2026-99727: Linux kernel · mm/huge_memory: properly handle refcounted PUD mappings on fork

Source GCVE Database

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

Not known to be exploited : upgrade to e8ebc5a46795cd1fb4333df81f19bbf458467cce or d90bdc02e36ec08d8248ebc6cdc52e12043eb28c 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 e8ebc5a46795cd1fb4333df81f19bbf458467cce, d90bdc02e36ec08d8248ebc6cdc52e12043eb28c

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 e8ebc5a46795cd1fb4333df81f19bbf458467cce or d90bdc02e36ec08d8248ebc6cdc52e12043eb28c.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ aed877c2b4257a25b2429f165542f86125871071, < e8ebc5a46795cd1fb4333df81f19bbf458467cce
Fixed in
  • e8ebc5a46795cd1fb4333df81f19bbf458467cce
LinuxLinuxAffected
  • ≥ aed877c2b4257a25b2429f165542f86125871071, < d90bdc02e36ec08d8248ebc6cdc52e12043eb28c
Fixed in
  • d90bdc02e36ec08d8248ebc6cdc52e12043eb28c
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: properly handle refcounted PUD mappings on fork copy_huge_pud() copies device-DAX entries without taking a folio reference or updating mapcounts and the child's RSS. For example, MADV_GUARD_INSTALL sets VM_MAYBE_GUARD on a device-DAX VMA, forcing copy_page_range() to traverse the whole VMA on fork. Any remaining huge PUDs are then copied without accounting for the new mappings. Unmapping them in the child decrements accounting that was never added. Use vm_normal_page_pud() to identify refcounted mappings. Take a folio reference and add the child's PUD rmap and RSS accounting before installing the copied entry. Pass src and dst VMAs consistently instead of src and dst MM. Move the TODO.

References

Community reviews

Loading reviews…