Skip to main content
VulnerabilityPublished

CVE-2026-99651: Linux kernel · mm/ksm: reset the unstable trees of all nodes

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99651· High

Not known to be exploited · fixed in 890e118e95bfc2aae4432ec2a95192d6f9193211 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 890e118e95bfc2aae4432ec2a95192d6f9193211, 31a2ba635adae60d23f744db2fef7ad318cdafa1, 7e5793cedeb444dc96b3b90e799d16f2f55d51b3 +1

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 Linux kernel to 890e118e95bfc2aae4432ec2a95192d6f9193211, 31a2ba635adae60d23f744db2fef7ad318cdafa1, 7e5793cedeb444dc96b3b90e799d16f2f55d51b3 or 1e59e96a064a6ca44e6fccb7a21f21d41614ff03.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ef53d16cded7f89b3843b7a96970dab897843ea5, < 890e118e95bfc2aae4432ec2a95192d6f9193211
Fixed in
  • 890e118e95bfc2aae4432ec2a95192d6f9193211
LinuxLinuxAffected
  • ≥ ef53d16cded7f89b3843b7a96970dab897843ea5, < 31a2ba635adae60d23f744db2fef7ad318cdafa1
Fixed in
  • 31a2ba635adae60d23f744db2fef7ad318cdafa1
LinuxLinuxAffected
  • ≥ ef53d16cded7f89b3843b7a96970dab897843ea5, < 7e5793cedeb444dc96b3b90e799d16f2f55d51b3
Fixed in
  • 7e5793cedeb444dc96b3b90e799d16f2f55d51b3
LinuxLinuxAffected
  • ≥ ef53d16cded7f89b3843b7a96970dab897843ea5, < 1e59e96a064a6ca44e6fccb7a21f21d41614ff03
Fixed in
  • 1e59e96a064a6ca44e6fccb7a21f21d41614ff03
LinuxLinuxAffected
  • =3.9
Fixed in–

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.

References

Community reviews

Loading reviews…