mm/huge_memory: fix truncate racing with PMD zapping
Summary
| CVE | CVE-2026-99669 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:01 UTC |
| Updated | 2026-11-22 11:17:05 UTC |
| 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 ] |
Risk And Classification
Primary CVSS: v3.1 7.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001560000 probability, percentile 0.047320000 (date 2026-11-21)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected fe6cf984939d8e12cb33a99673c8d026c5135e68 a5786ec7ba7967433207f20214ff75768497a2c9 git | Not specified |
| CNA | Linux | Linux | affected fe6cf984939d8e12cb33a99673c8d026c5135e68 e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4 git | Not specified |
| CNA | Linux | Linux | affected 79d8c89baa10612c1675972a632c65cdbe0936f6 git | Not specified |
| CNA | Linux | Linux | affected 13f4910d81b62a214cdb28b47237198fa96078a2 git | Not specified |
| CNA | Linux | Linux | affected 7a4c3f7b47ba34b021a7747081f330bfb76a4271 git | Not specified |
| CNA | Linux | Linux | affected 6e904f9e8cb0e39f60e1cdbea679f89346a563c2 git | Not specified |
| CNA | Linux | Linux | affected fd720d3906877b3d2118cd480027e4bc6648f0c5 git | Not specified |
| CNA | Linux | Linux | affected effe3cc6d4fdd407457eb30f7b0ef094393f0d64 git | Not specified |
| CNA | Linux | Linux | affected 9435cddf1378d149d826bd7bd1448a44bf96868d git | Not specified |
| CNA | Linux | Linux | affected 5.10.273 5.11 semver | Not specified |
| CNA | Linux | Linux | affected 5.15.224 5.16 semver | Not specified |
| CNA | Linux | Linux | affected 6.1.191 6.2 semver | Not specified |
| CNA | Linux | Linux | affected 6.6.160 6.7 semver | Not specified |
| CNA | Linux | Linux | affected 6.12.114 6.13 semver | Not specified |
| CNA | Linux | Linux | affected 6.18.52 6.19 semver | Not specified |
| CNA | Linux | Linux | affected 7.2.5 7.3 semver | Not specified |
| CNA | Linux | Linux | affected 7.3 | Not specified |
| CNA | Linux | Linux | unaffected 7.3 semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3.5 7.3.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.4-rc2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a5786ec7ba7967433207f20214ff75768497a2c9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.