CVE-2026-99735
mm/mglru: don't use stack pointers when walking PUD and PMD tables
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: ]
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e (affected, git) ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 4b428d9d24e303f92819119c66858f5de38bbc78 (affected, git) ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 (affected, git) ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 65a9bf08a3e4d6e58df211ed900c16bafb79b267 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
6.1 (affected) ≥ 0; < 6.1 (unaffected, semver) ≥ 6.12.118; ≤ 6.12.* (unaffected, semver) ≥ 6.18.64; ≤ 6.18.* (unaffected, semver) ≥ 7.3.5; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44eCNA: Linux
- https://git.kernel.org/stable/c/4b428d9d24e303f92819119c66858f5de38bbc78CNA: Linux
- https://git.kernel.org/stable/c/4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3CNA: Linux
- https://git.kernel.org/stable/c/65a9bf08a3e4d6e58df211ed900c16bafb79b267CNA: Linux
- https://git.kernel.org/stable/c/4b428d9d24e303f92819119c66858f5de38bbc78416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/65a9bf08a3e4d6e58df211ed900c16bafb79b267416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.