* CVE-2026-99651: mm/ksm: reset the unstable trees of all nodes
@ 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/ksm: reset the unstable trees of all nodes
Each full scan resets ksm_nr_node_ids unstable tree roots. Enabling
merge_across_nodes resets this count to 1, even if per-node roots were
previously allocated.
So when toggling "merge_across_nodes" 0 -> 1 -> 0, a scan that starts
while the setting is 1 and continues after switching back to 0 can
encounter stale unstable tree roots, resulting in UAF.
Only root is allowed to change "merge_across_nodes", and the documented
sequence is: "merge_across_nodes setting can be changed only when there
are no ksm shared pages in the system: set run 2 to unmerge pages first,
then to 1 after changing merge_across_nodes, to remerge according to the
new setting."
Let's fix it by tracking in ksm_nr_node_ids the actual number of
allocated tree roots.
remove_all_stable_nodes() and ksm_check_stable_tree() will now scan
more tree roots (skipping the empty ones), which is harmless.
The Linux kernel CVE team has assigned CVE-2026-99651 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.9 with commit ef53d16cded7f89b3843b7a96970dab897843ea5 and fixed in 6.12.118 with commit 7e5793cedeb444dc96b3b90e799d16f2f55d51b3
Issue introduced in 3.9 with commit ef53d16cded7f89b3843b7a96970dab897843ea5 and fixed in 6.18.64 with commit 1e59e96a064a6ca44e6fccb7a21f21d41614ff03
Issue introduced in 3.9 with commit ef53d16cded7f89b3843b7a96970dab897843ea5 and fixed in 7.3.5 with commit 31a2ba635adae60d23f744db2fef7ad318cdafa1
Issue introduced in 3.9 with commit ef53d16cded7f89b3843b7a96970dab897843ea5 and fixed in 7.4-rc2 with commit 890e118e95bfc2aae4432ec2a95192d6f9193211
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-99651
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/ksm.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/7e5793cedeb444dc96b3b90e799d16f2f55d51b3
https://git.kernel.org/stable/c/1e59e96a064a6ca44e6fccb7a21f21d41614ff03
https://git.kernel.org/stable/c/31a2ba635adae60d23f744db2fef7ad318cdafa1
https://git.kernel.org/stable/c/890e118e95bfc2aae4432ec2a95192d6f9193211
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-11-20 5:56 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-99651: mm/ksm: reset the unstable trees of all nodes 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.