Skip to main content
VulnerabilityPublished

CVE-2026-99567: Linux kernel · assoc_array: don't chain a new shortcut onto an existing one

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in a7990a72267f264f5284f6bcb90d397b29ac00ed : 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 a7990a72267f264f5284f6bcb90d397b29ac00ed, 258745fea55ba057c062e0e680a54fde26630e95, 517e7bbfaf5381d47e8d393ff54c61107f8fb1bb

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 a7990a72267f264f5284f6bcb90d397b29ac00ed, 258745fea55ba057c062e0e680a54fde26630e95 or 517e7bbfaf5381d47e8d393ff54c61107f8fb1bb.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3cb989501c2688cacbb7dc4b0d353faf838f53a1, < a7990a72267f264f5284f6bcb90d397b29ac00ed
Fixed in
  • a7990a72267f264f5284f6bcb90d397b29ac00ed
LinuxLinuxAffected
  • ≥ 3cb989501c2688cacbb7dc4b0d353faf838f53a1, < 258745fea55ba057c062e0e680a54fde26630e95
Fixed in
  • 258745fea55ba057c062e0e680a54fde26630e95
LinuxLinuxAffected
  • ≥ 3cb989501c2688cacbb7dc4b0d353faf838f53a1, < 517e7bbfaf5381d47e8d393ff54c61107f8fb1bb
Fixed in
  • 517e7bbfaf5381d47e8d393ff54c61107f8fb1bb
LinuxLinuxAffected
  • =3.13
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: assoc_array: don't chain a new shortcut onto an existing one When a full node's leaves and the new key all share the node's segment, assoc_array_insert_into_terminal_node() replaces the node with a shortcut to a pair of new nodes. If the node is itself the target of a shortcut, the new shortcut is installed as that shortcut's next node, and a shortcut leading to a shortcut is something nothing expects: assoc_array_walk() indexes the second one as a node, and assoc_array_apply_edit() hits the BUG_ON() in the loop that adjusts nr_leaves_on_branch, on that same insertion. Deletion gets a node there. When the subtree below a shortcut shrinks enough, assoc_array_delete() collapses it into one node below the shortcut, and the leaves it collects can all share that node's segment. The next key that shares it too takes this path. Eighteen insertions and a deletion are enough: sixteen keys that agree on bits 0-11, one that leaves them at bit 8 and is deleted again, and one more that agrees with the sixteen. Have the new shortcut replace the one in front of the node as well. assoc_array_insert_shortcut() gives it that shortcut's back pointer and parent slot, so the caller installs it where that one was, and excises the old shortcut along with the node, which takes a second entry in excised_meta[]. The new shortcut's index key comes from the new key up to the new skip level, so it covers what the old one did. Found by a userspace test doing random insertions and deletions on keys that share long prefixes; a targeted case builds a shortcut, deletes down to the collapse and inserts one more key.

References

Community reviews

Loading reviews…