Skip to main content
Menu
CVEs

Linux kernel crash via truncate race in huge memory PMD zapping

CVE-2026-99669Published November 20, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 5.11, 5.16, 6.2, 6.7, 6.13, and 2 more
Who is exposed
Not reported

Summary

In the Linux kernel's memory management code, a race between truncating a file and zapping a huge page table entry can leave a folio marked dirty after it is no longer mapped, which can cause a kernel crash (oops) on XFS when MADV_DONTNEED races with ftruncate(). The affected software is Linux.

Written by a model

Original description

In the Linux kernel, the following vulnerability has been resolved:

mm/huge_memory: fix truncate racing with PMD zapping

zap_huge_pmd_folio() removes the rmap before calling folio_mark_dirty(). If this was the last mapping, truncation can skip unmapping the folio and proceed without waiting for the PMD lock, racing with dirtying.

ifs_set_range_dirty() can oops if MADV_DONTNEED races with ftruncate() on XFS, when we get the folio set dirty after it was found to not be mapped anymore.

Move folio_mark_dirty() and folio_mark_accessed() before rmap removal, matching the PTE zap path. This keeps the folio mapped while updating its state, so truncation must wait for the page table lock.

Fix generated by an LLM and sent by Chris Mason in private.

[ david: simplify comment and description ]

What to do

Upgrade to a fixed version: 5.11, 5.16, 6.2, 6.7, 6.13, or one of 2 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99669 (mm/huge_memory: fix truncate racing with PMD zapping), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99669 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 5.10.273, fixed in 5.11; from 5.15.224, fixed in 5.16; from 6.1.191, fixed in 6.2; from 6.6.160, fixed in 6.7; from 6.12.114, fixed in 6.13; from 6.18.52, fixed in 6.19; from 7.2.5, fixed in 7.3
- Linux Linux: versions 7.3
Fixed versions: 5.11, 5.16, 6.2, 6.7, 6.13, 6.19, 7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99669 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99669 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/a5786ec7ba7967433207f20214ff75768497a2c9
- https://git.kernel.org/stable/c/e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99669
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99669"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

Questions about CVE-2026-99669

Is CVE-2026-99669 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99669?

Linux: from 5.10.273 before 5.11; from 5.15.224 before 5.16; from 6.1.191 before 6.2; from 6.6.160 before 6.7; from 6.12.114 before 6.13; from 6.18.52 before 6.19; from 7.2.5 before 7.3. Linux: version 7.3.

Source: cve.now feed data

How do I fix CVE-2026-99669?

Upgrade to a fixed version: 5.11, 5.16, 6.2, 6.7, 6.13, or one of 2 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.