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

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e (affected, git); ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 4b428d9d24e303f92819119c66858f5de38bbc78 (affected, git); ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 (affected, git); ≥ bd74fdaea146029e4fa12c6de89adbe0779348a9; < 65a9bf08a3e4d6e58df211ed900c16bafb79b267 (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.20%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e (CNA: Linux)

- https://git.kernel.org/stable/c/4b428d9d24e303f92819119c66858f5de38bbc78 (CNA: Linux)

- https://git.kernel.org/stable/c/4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 (CNA: Linux)

- https://git.kernel.org/stable/c/65a9bf08a3e4d6e58df211ed900c16bafb79b267 (CNA: Linux)

- https://git.kernel.org/stable/c/4b428d9d24e303f92819119c66858f5de38bbc78 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/4e5eb180d37cb222ed3c9b6772c6044e16c2a1c3 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/65a9bf08a3e4d6e58df211ed900c16bafb79b267 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/a352391f8f9c035d3b2a8a9fe6e3fd2e1c4ec44e (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99735; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99735; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99735; retrieved 2026-11-22; source updated Not reported

Revision: d50a461b30ad232d3442d1bd808a94e701c727ead5423dddeba4c84f53a9a40e

Canonical: https://y2.dev/cve/CVE-2026-99735

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.