Tools
Log in
English

Learn to codeSecurity check

CVE-2026-99735

HighCVSS 7.8

CVE-2026-99735 High 7.8 · Linux kernel · Linux · details and fixes

Severity
High
Score
7.8 · CVSS 3.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Product
Linux kernel · Linux
Published
2026-11-20
Last modified
2026-11-22
Exploitation
Not on the exploited list

Description

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: ]

Related fix guides

L04Pending security updatesL05New kernel installed, no reboot

Back to the CVE list