Skip to main content
VulnerabilityPublished

CVE-2026-99664: Linux kernel · mm/gup: recheck the PUD under PTL in follow_pud_mask()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in da57b6bce646946c083a48df644d43bb9d011f5f : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in da57b6bce646946c083a48df644d43bb9d011f5f, 79cb51d538abc459f74e046d27797d36b133ce0e, 9eaedd598cd25eb0e18958e2456153a4c1f3db03

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to da57b6bce646946c083a48df644d43bb9d011f5f, 79cb51d538abc459f74e046d27797d36b133ce0e or 9eaedd598cd25eb0e18958e2456153a4c1f3db03.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1b1676180246232308885c4f37fee01cf898fdb2, < da57b6bce646946c083a48df644d43bb9d011f5f
Fixed in
  • da57b6bce646946c083a48df644d43bb9d011f5f
LinuxLinuxAffected
  • ≥ 1b1676180246232308885c4f37fee01cf898fdb2, < 79cb51d538abc459f74e046d27797d36b133ce0e
Fixed in
  • 79cb51d538abc459f74e046d27797d36b133ce0e
LinuxLinuxAffected
  • ≥ 1b1676180246232308885c4f37fee01cf898fdb2, < 9eaedd598cd25eb0e18958e2456153a4c1f3db03
Fixed in
  • 9eaedd598cd25eb0e18958e2456153a4c1f3db03
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

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.

References

Community reviews

Loading reviews…