* CVE-2026-99669: mm/huge_memory: fix truncate racing with PMD zapping
@ 2026-11-20 5:50 Greg Kroah-Hartman
0 siblings, 0 replies; only message in thread
From: Greg Kroah-Hartman @ 2026-11-20 5:50 UTC (permalink / raw)
To: linux-cve-announce; +Cc: Greg Kroah-Hartman
From: Greg Kroah-Hartman <gregkh@kernel.org>
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 ]
The Linux kernel CVE team has assigned CVE-2026-99669 to this issue.
Affected and fixed versions
===========================
Issue introduced in 7.3 with commit fe6cf984939d8e12cb33a99673c8d026c5135e68 and fixed in 7.3.5 with commit a5786ec7ba7967433207f20214ff75768497a2c9
Issue introduced in 7.3 with commit fe6cf984939d8e12cb33a99673c8d026c5135e68 and fixed in 7.4-rc2 with commit e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4
Issue introduced in 5.10.273 with commit 79d8c89baa10612c1675972a632c65cdbe0936f6
Issue introduced in 5.15.224 with commit 13f4910d81b62a214cdb28b47237198fa96078a2
Issue introduced in 6.1.191 with commit 7a4c3f7b47ba34b021a7747081f330bfb76a4271
Issue introduced in 6.6.160 with commit 6e904f9e8cb0e39f60e1cdbea679f89346a563c2
Issue introduced in 6.12.114 with commit fd720d3906877b3d2118cd480027e4bc6648f0c5
Issue introduced in 6.18.52 with commit effe3cc6d4fdd407457eb30f7b0ef094393f0d64
Issue introduced in 7.2.5 with commit 9435cddf1378d149d826bd7bd1448a44bf96868d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99669
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
mm/huge_memory.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a5786ec7ba7967433207f20214ff75768497a2c9
https://git.kernel.org/stable/c/e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-11-20 5:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20 5:50 CVE-2026-99669: mm/huge_memory: fix truncate racing with PMD zapping Greg Kroah-Hartman
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.