Bug 2577801 (CVE-2026-99727) - CVE-2026-99727 kernel: kernel: memory corruption via improper reference counting of huge page mappings on fork
Summary: CVE-2026-99727 kernel: kernel: memory corruption via improper reference count...
Keywords:
Status: NEW
Alias: CVE-2026-99727
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:14 UTC by OSIDB Bzimport
Modified: 2026-11-20 11:21 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:14:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.