bpf: Reject resilient lock operations in rbtree callbacks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.18.53, Kernel 7.2.7, Kernel 7b7b8b5960102566bd625ae829d1f330c5b5d104 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject resilient lock operations in rbtree callbacks __bpf_rbtree_add() keeps parent and link pointers live across calls to the program-supplied comparison callback. The verifier therefore requires the root's lock to remain held throughout the callback. The helper path enforces this rule for bpf_spin_lock() and bpf_spin_unlock(), but the resilient lock kfunc argument path does not. Since resilient locks may protect BPF rbtree roots, a callback can release the root lock and let another CPU remove and free the node referenced by the in-progress tree walk. The walk then resumes using freed pointers. Reject resilient lock kfuncs in an rbtree comparison callback, matching the existing policy for the spin lock helpers. Resilient-lock-protected trees remain valid when their comparison callbacks leave lock state alone.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=6.15 <6.18.53, >=6.19 <7.2.7, =7.3, >=0de2046137f976e7302d43ac01d9894d07ac1fff <7b7b8b5960102566bd625ae829d1f330c5b5d104, >=0de2046137f976e7302d43ac01d9894d07ac1fff <cc2e065ed206aecd9b94564779244f3ffb26e356, =6.15, >=0de2046137f976e7302d43ac01d9894d07ac1fff <71930202a0a0c49f0a3b45b41907a074cb780266 | 6.18.53, 7.2.7, 7b7b8b5960102566bd625ae829d1f330c5b5d104, cc2e065ed206aecd9b94564779244f3ffb26e356, 71930202a0a0c49f0a3b45b41907a074cb780266 |
| linux-kernel: Kernel | >=6.15.0 <6.18.53, >=6.19.0 <7.2.7 | 6.18.53, 7.2.7 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket