GHSA-PPG8-FF2J-7W83

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99651"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:58Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/ksm: reset the unstable trees of all nodes\n\nEach full scan resets ksm_nr_node_ids unstable tree roots. Enabling\nmerge_across_nodes resets this count to 1, even if per-node roots were\npreviously allocated.\n\nSo when toggling \"merge_across_nodes\" 0 -\u003e 1 -\u003e 0, a scan that starts\nwhile the setting is 1 and continues after switching back to 0 can\nencounter stale unstable tree roots, resulting in UAF.\n\nOnly root is allowed to change \"merge_across_nodes\", and the documented\nsequence is: \"merge_across_nodes setting can be changed only when there\nare no ksm shared pages in the system: set run 2 to unmerge pages first,\nthen to 1 after changing merge_across_nodes, to remerge according to the\nnew setting.\"\n\nLet\u0027s fix it by tracking in ksm_nr_node_ids the actual number of\nallocated tree roots.\n\nremove_all_stable_nodes() and ksm_check_stable_tree() will now scan\nmore tree roots (skipping the empty ones), which is harmless.",
  "id": "GHSA-ppg8-ff2j-7w83",
  "modified": "2026-11-20T06:32:05Z",
  "published": "2026-11-20T06:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99651"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1e59e96a064a6ca44e6fccb7a21f21d41614ff03"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/31a2ba635adae60d23f744db2fef7ad318cdafa1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7e5793cedeb444dc96b3b90e799d16f2f55d51b3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/890e118e95bfc2aae4432ec2a95192d6f9193211"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.