PT-2026-152615

CVE-2026-99735

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
mm/mglru: don't use stack pointers when walking PUD and PMD tables
MGLRU passes stack copies of page-table entries in walk pud range() and walk pmd range() when walking to the next level. These copies can become stale when khugepaged or MADV DONTNEED (CONFIG PT RECLAIM) removes a PTE table concurrently.
This pattern dates back to commit bd74fdaea146 ("mm: multi-gen LRU: support page table walks"). Likely, earlier locking masked the latent bug. Later changes exposed it: commit 1d65b771bc08 ("mm/khugepaged: retract page tables() without mmap or vma lock") allowed concurrent retraction, and commit cf4a65539c13 ("memcg-v1: no need for memcg locking for MGLRU") dropped the walker's outer RCU protection.
The fix is simple, so just fix the original commit so we don't have to speculate. To fix it, pass the actual PMD/PUD pointers. This restores the RCU-protected lookup and validation against the live PMD. Note that the PUD handling is required as well to handle folded page tables correctly in all cases.
Fix generated by an LLM and sent by Josef Bacik in private.
[ david: handle walk pud range() as well, clarify+simplify description, adjust Fixes: ]
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾