Skip to main content
VulnerabilityPublished

CVE-2026-99669: Linux kernel · mm/huge_memory: fix truncate racing with PMD zapping

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4, a5786ec7ba7967433207f20214ff75768497a2c9, 7.3 +6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.10.273 <5.11
  • >=5.15.224 <5.16
  • >=6.1.191 <6.2
  • >=6.6.160 <6.7
  • >=6.12.114 <6.13
  • >=6.18.52 <6.19
  • >=7.2.5 <7.3
Fixed in
  • e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4
  • a5786ec7ba7967433207f20214ff75768497a2c9
  • 7.3
  • 6.19
  • 6.13
  • 6.7
  • 6.2
  • 5.16
  • 5.11
LinuxLinuxAffected
  • =7.3
Fixed in–

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 ]

References

Community reviews

Loading reviews…