# CVE-2026-99669: mm/huge_memory: fix truncate racing with PMD zapping

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

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 ]

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ fe6cf984939d8e12cb33a99673c8d026c5135e68; < a5786ec7ba7967433207f20214ff75768497a2c9 (affected, git); ≥ fe6cf984939d8e12cb33a99673c8d026c5135e68; < e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4 (affected, git); 79d8c89baa10612c1675972a632c65cdbe0936f6 (affected, git); 13f4910d81b62a214cdb28b47237198fa96078a2 (affected, git); 7a4c3f7b47ba34b021a7747081f330bfb76a4271 (affected, git); 6e904f9e8cb0e39f60e1cdbea679f89346a563c2 (affected, git); fd720d3906877b3d2118cd480027e4bc6648f0c5 (affected, git); effe3cc6d4fdd407457eb30f7b0ef094393f0d64 (affected, git); 9435cddf1378d149d826bd7bd1448a44bf96868d (affected, git); ≥ 5.10.273; < 5.11 (affected, semver); ≥ 5.15.224; < 5.16 (affected, semver); ≥ 6.1.191; < 6.2 (affected, semver); ≥ 6.6.160; < 6.7 (affected, semver); ≥ 6.12.114; < 6.13 (affected, semver); ≥ 6.18.52; < 6.19 (affected, semver); ≥ 7.2.5; < 7.3 (affected, semver). Source: CNA: Linux
- Linux / Linux: 7.3 (affected); ≥ 0; < 7.3 (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.16% as of 2026-11-21; percentile 4.73%

- 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/a5786ec7ba7967433207f20214ff75768497a2c9 (CNA: Linux)

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

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

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

## Provenance

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

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

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

Revision: f3d35752dd8d8d0e1ae6338b57997e70caa82462854591c8e03d505a131a62d3

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

## 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.