Skip to main content
VulnerabilityPublished

CVE-2026-99735: Linux kernel · mm/mglru: don't use stack pointers when walking PUD and PMD tables

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99735· Medium

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

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e, 65a9bf08a3e4d6e58df211ed900c16bafb79b267, 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 +1

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 a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e, 65a9bf08a3e4d6e58df211ed900c16bafb79b267, 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 or 4b428d9d24e303f92819119c66858f5de38bbc78.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9, < a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e
Fixed in
  • a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e
LinuxLinuxAffected
  • ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9, < 65a9bf08a3e4d6e58df211ed900c16bafb79b267
Fixed in
  • 65a9bf08a3e4d6e58df211ed900c16bafb79b267
LinuxLinuxAffected
  • ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9, < 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3
Fixed in
  • 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3
LinuxLinuxAffected
  • ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9, < 4b428d9d24e303f92819119c66858f5de38bbc78
Fixed in
  • 4b428d9d24e303f92819119c66858f5de38bbc78
LinuxLinuxAffected
  • =6.1
Fixed in–

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

References

Community reviews

Loading reviews…