Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99506

mm/hugetlb: fix use-after-free of a new anon folio

No exploitation reported by the sources we read.

  • Published2026-11-19
  • Fixed in7.3.2 · 6.18.61 · 6.12.117

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix use-after-free of a new anon folio For a fault in a private mapping with nothing in the page cache, hugetlb_no_page() allocates a folio, locks it and maps it. The folio has one reference, which belongs to the page table entry from then on. After dropping the page table lock the function still sets the migratable flag of the folio and unlocks it. Whoever zaps the entry in between frees the folio. The fault holds the fault mutex and the lock of the vma. MADV_DONTNEED and the first unmap of a hole punch, hugetlb_vmdelete_list(), do not take the fault mutex, and a private vma only has a lock if it owns a reservation map: not with MAP_NORESERVE, and not in the child after fork(). Then the flag is set in, and folio_unlock() is called on, a folio that is free or has a new owner. A surplus page goes back to the page allocator while it is locked: BUG: Bad page state in process init pfn:108e00 flags: 0x200000000000059(locked|uptodate|dirty|head|node=0|zone=2) page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set A page of the pool can be given to the next user, of any file, who locks it and loses the lock to the late folio_unlock(): kernel BUG at mm/filemap.c:1532! hugetlb_no_page+0x111b/0x23e0 hugetlb_fault+0x3a9/0x14a0 An unprivileged process is enough: threads that write to a MAP_PRIVATE | MAP_NORESERVE hugetlb mapping, threads that call MADV_DONTNEED on it, and one that takes the freed pages for another file. Until commit 3a47c54f09c4 ("hugetlbfs: revert use i_mmap_rwsem for more pmd sharing synchronization") the fault held i_mmap_rwsem for reading, which everybody who zaps takes for writing. The lock that commit bf4916922c60 ("hugetlbfs: extend hugetlb_vma_lock to private VMAs") gave to private vmas closed the window again, but only for those with a reservation map. Be done with the folio before the page table lock is dropped, as hugetlb_wp() is with its copy. The function already unlocks page cache folios under that lock. Original fix generated by an LLM and sent in private by Josef. [david@kernel.org: simplify+move comment]

Timeline

dates in UTC
  1. 2026-11-1914:43CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.13.0, < 6.18.616.18.61
6.x≥ 6.1.0, < 6.12.1176.12.117

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 3a47c54f09c4c89128d8f67d49296b1c25b317d0, < 727dfb28c6a2334f08cdaef82540137c9b094ab7fixed in 727dfb28c6a2334f08cdaef82540137c9b094ab7git
    • ≥ 3a47c54f09c4c89128d8f67d49296b1c25b317d0, < 1108d9a51c91bb459fa62506fd0176dc9e0927c5fixed in 1108d9a51c91bb459fa62506fd0176dc9e0927c5git
    • ≥ 3a47c54f09c4c89128d8f67d49296b1c25b317d0, < 51b21515bdac0a60efac142dbfa44481e4206f28fixed in 51b21515bdac0a60efac142dbfa44481e4206f28git
    • ≥ 3a47c54f09c4c89128d8f67d49296b1c25b317d0, < 824cc56bf43c714319992bad3558803cac6e77c0fixed in 824cc56bf43c714319992bad3558803cac6e77c0git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.1no fix stated

    Not affected < 6.1 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAzure Linux:3all versions · no fixed version listed
  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linuxDebian:12all versions · no fixed version listed
  • linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
  • linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
  • linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed

Vendor advisories

  • CVE-2026-99506 Red Hat Product Security125 known affected

    kernel: kernel: Denial of Service via use-after-free in hugetlb

    kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +122 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99506 · 111 productsFix deferred
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-99506 · 14 productsOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-19
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-m64r-vrqc-r265

Frequently asked questions

What is CVE-2026-99506?

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix use-after-free of a new anon folio For a fault in a private mapping with nothing in the page cache, hugetlb_no_page() allocates a folio, locks it and maps it. The folio has one reference, which belongs to the page table entry from then on. After dropping the page table lock the function still sets the migratable flag of the folio and unlocks it. Whoever zaps the entry in between frees the folio. The fault holds the fault mutex and the lock of the vma. MADV_DONTNEED and the first unmap of a hole punch, hugetlb_vmdelete_list(), do not take the fault mutex, and a private vma only has a lock if it owns a reservation map: not with MAP_NORESERVE, and not in the child after fork(). Then the flag is set in, and folio_unlock() is called on, a folio that is free or has a new owner. A surplus page goes back to the page allocator while it is locked: BUG: Bad page state in process init pfn:108e00 flags: 0x200000000000059(locked|uptodate|dirty|head|node=0|zone=2) page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set A page of the pool can be given to the next user, of any file, who locks it and loses the lock to the late folio_unlock(): kernel BUG at mm/filemap.c:1532! hugetlb_no_page+0x111b/0x23e0 hugetlb_fault+0x3a9/0x14a0 An unprivileged process is enough: threads that write to a MAP_PRIVATE | MAP_NORESERVE hugetlb mapping, threads that call MADV_DONTNEED on it, and one that takes the freed pages for another file. Until commit 3a47c54f09c4 ("hugetlbfs: revert use i_mmap_rwsem for more pmd sharing synchronization") the fault held i_mmap_rwsem for reading, which everybody who zaps takes for writing. The lock that commit bf4916922c60 ("hugetlbfs: extend hugetlb_vma_lock to private VMAs") gave to private vmas closed the window again, but only for those with a reservation map. Be done with the folio before the page table lock is dropped, as hugetlb_wp() is with its copy. The function already unlocks page cache folios under that lock. Original fix generated by an LLM and sent in private by Josef. [david@kernel.org: simplify+move comment]

Is CVE-2026-99506 actively exploited?

Active exploitation of CVE-2026-99506 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99506?

CVE-2026-99506 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record