CVE-2026-99664

published 20 Nov 2026 · updated 20 Nov 2026

mm/gup: recheck the PUD under PTL in follow_pud_mask()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 79cb51d538abc459f74e046d27797d36b133ce0e, Kernel 9eaedd598cd25eb0e18958e2456153a4c1f3db03, Kernel da57b6bce646946c083a48df644d43bb9d011f5f and 2 more.

In the Linux kernel, the following vulnerability has been resolved: mm/gup: recheck the PUD under PTL in follow_pud_mask() follow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes the lock and calls follow_huge_pud(), which reads the entry again, but only tests whether it is present. A leaf can be zapped concurrently and a page fault can fill the empty entry with a page table. This currently only applies when device-dax makes use of PUD entries, and the fault after e.g., MADV_DONTNEED would find THPs to be disabled. That requires a sequence like 1) Fault in the PUD 2) Disable THP 3) Have GUP race against concurrent MADV_DONTNEED + refault Which is rather unlikely to happen in practice, which is why we never received a report about such a problem. Before commit 1b1676180246 ("mm/gup: handle huge pud for follow_pud_mask()"), we performed that check in follow_devmap_pud() by testing for pud_devmap(). Let's fix it by just structuring follow_pud_mask() similar to follow_pmd_mask(), minus protnone stuff that does not apply and minus FOLL_SPLIT_PMD handling. That makes it much easier to spot any such inconsistencies. Perform the pud_bad() check early in follow_pmd_mask() and just forward the PUD value. We can drop the pud_present() check in follow_huge_pud(), just like we have in follow_huge_pmd(). Even though we are performing more changes than strictly necessary, the fix should be easy to backport.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.10, >=1b1676180246232308885c4f37fee01cf898fdb2 <79cb51d538abc459f74e046d27797d36b133ce0e, >=1b1676180246232308885c4f37fee01cf898fdb2 <9eaedd598cd25eb0e18958e2456153a4c1f3db03, >=1b1676180246232308885c4f37fee01cf898fdb2 <da57b6bce646946c083a48df644d43bb9d011f5f79cb51d538abc459f74e046d27797d36b133ce0e, 9eaedd598cd25eb0e18958e2456153a4c1f3db03, da57b6bce646946c083a48df644d43bb9d011f5f
linux-kernel: Kernel>=6.10.0 <6.18.64, >=6.19.0 <7.3.56.18.64, 7.3.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99664 severity on Zeptric[![CVE-2026-99664](https://zeptric.io/badge/cve/CVE-2026-99664.svg)](https://zeptric.io/cve/CVE-2026-99664)