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

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/hugememory: properly handle refcounted PUD mappings on fork

copyhugepud() copies device-DAX entries without taking a folio reference or updating mapcounts and the child's RSS.

For example, MADVGUARDINSTALL sets VMMAYBEGUARD on a device-DAX VMA, forcing copypagerange() 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 vmnormalpagepud() 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.

Affected Software

3 affected componentsFixes available
linux/kernel>=6.15.0<7.3.5
7.3.5
debian/linux*
debian/linux<=7.3.4-1
6.1.176-16.1.192-26.12.107-16.12.117-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which workloads are exposed to the affected path?

The affected path involves processes that fork while using device-DAX VMAs containing huge PUD mappings. The description specifically notes that MADV_GUARD_INSTALL can set VM_MAYBE_GUARD on such a VMA, causing fork processing to traverse the VMA and copy remaining huge PUD entries.

2

What happens after an affected mapping is copied into a child process?

The copied device-DAX huge PUD entry may be installed without taking a folio reference or updating the child mapping counts and RSS. If the child later unmaps it, accounting is decremented even though it was never added.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203