CVE-2026-99506: mm/hugetlb: fix use-after-free of a new anon folio
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, hugetlbnopage() 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. MADVDONTNEED and the first unmap of a hole punch, hugetlbvmdeletelist(), do not take the fault mutex, and a private vma only has a lock if it owns a reservation map: not with MAPNORESERVE, and not in the child after fork().
Then the flag is set in, and foliounlock() 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: PAGEFLAGSCHECKATFREE 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 foliounlock():
kernel BUG at mm/filemap.c:1532! hugetlbnopage+0x111b/0x23e0 hugetlbfault+0x3a9/0x14a0
An unprivileged process is enough: threads that write to a MAPPRIVATE | MAPNORESERVE hugetlb mapping, threads that call MADVDONTNEED on it, and one that takes the freed pages for another file.
Until commit 3a47c54f09c4 ("hugetlbfs: revert use immaprwsem for more pmd sharing synchronization") the fault held immaprwsem for reading, which everybody who zaps takes for writing. The lock that commit bf4916922c60 ("hugetlbfs: extend hugetlbvmalock 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 hugetlbwp() 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]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2