CVE-2026-99566: assoc_array: keep gc's cleanup out of the live tree on allocation failure
In the Linux kernel, the following vulnerability has been resolved:
assocarray: keep gc's cleanup out of the live tree on allocation failure
assocarraygc() builds a copy of the tree. Where the copy reaches a shortcut, it allocates the copy of the shortcut with kmallocflex(), fills it with memcpy(), links it into the new tree, and only then allocates the copy of the node after it. The memcpy() leaves the new shortcut's nextnode pointing at the old tree's node, so if that second allocation fails, the cleanup, assocarraydestroysubtree() on the new tree, follows the new shortcut into the old tree, and the BUGON() on the old node's back pointer fires.
Allocate the node first, and the shortcut once the node exists, freeing the node again if the shortcut cannot be allocated. A copied shortcut is then only linked into the new tree when the copy of its node is there to follow it. Nothing else changes: with no allocation failing, the trees gc builds are the same as before.
Found by a userspace test that makes each allocation of each operation fail in turn.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What condition is required to trigger the failure?
An allocation must fail while assoc_array_gc() is copying a tree at a shortcut: specifically, after the shortcut copy is linked into the new tree but before allocation of the following node succeeds.
What is the observable result of a successful trigger?
Cleanup of the partially built tree can follow the copied shortcut into the old live tree, causing the BUG_ON() on the old node's back pointer to fire.
Is normal garbage-collection behavior changed when allocations succeed?
No. The fix states that when no allocation fails, the trees built by garbage collection are unchanged.
What mitigation is indicated if the fix cannot be applied immediately?
The provided data identifies allocation failure during assoc_array_gc() as the trigger, but does not provide a configuration workaround or other mitigation.