bpf: Clear rb node linkage when freeing bpf_rb_root
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
1d0675957d35ac5e514073481beda62e4e1e2ec5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Clear rb node linkage when freeing bpf_rb_root
bpf_rb_root_free() detaches the root by copying the current rb_root_cached and then replacing the live root with RB_ROOT_CACHED. It then walks the copied root and drops each object contained in the tree.
This leaves the rb node state intact while dropping the object. If the object is refcounted and survives the drop, its bpf_rb_node_kern still contains an owner pointer to the freed root and stale rb tree linkage. If a later bpf_rb_root allocation reuses the same address, bpf_rbtree_remove() can incorrectly pass the owner check and call rb_erase_cached() on a node whose rb pointers belong to the old tree.
Mirror the list draining behavior by marking nodes as busy while the root is being detached, then clear the rb node and release the owner before dropping the containing object. This makes surviving nodes unowned and safe to reject from remove or accept for a later add.
From the CVE record · Linux
The Linux kernel’s BPF rb_root cleanup can leave stale tree linkage in a refcounted object that survives release. If a later root allocation reuses the same address, removing that object can incorrectly operate on pointers from the old tree. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with BPF support should check their kernel versions against the vendor advisory; affected versions are not specified.