CVE-2024-35860

published 19 May 2024 · updated 30 Oct 2026

bpf: support deferring bpf_link dealloc to after RCU grace period

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce, Kernel 5d8d447777564b35f67000e7838e7ccb64d525c8, Kernel 876941f533e7b47fc69977fc4551c02f2d18af97 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: bpf: support deferring bpf_link dealloc to after RCU grace period BPF link for some program types is passed as a "context" which can be used by those BPF programs to look up additional information. E.g., for multi-kprobes and multi-uprobes, link is used to fetch BPF cookie values. Because of this runtime dependency, when bpf_link refcnt drops to zero there could still be active BPF programs running accessing link data. This patch adds generic support to defer bpf_link dealloc callback to after RCU GP, if requested. This is done by exposing two different deallocation callbacks, one synchronous and one deferred. If deferred one is provided, bpf_link_free() will schedule dealloc_deferred() callback to happen after RCU GP. BPF is using two flavors of RCU: "classic" non-sleepable one and RCU tasks trace one. The latter is used when sleepable BPF programs are used. bpf_link_free() accommodates that by checking underlying BPF program's sleepable flag, and goes either through normal RCU GP only for non-sleepable, or through RCU tasks trace GP *and* then normal RCU GP (taking into account rcu_trace_implies_rcu_gp() optimization), if BPF program is sleepable. We use this for multi-kprobe and multi-uprobe links, which dereference link during program run. We also preventively switch raw_tp link to use deferred dealloc callback, as upcoming changes in bpf-next tree expose raw_tp link data (specifically, cookie value) to BPF program at runtime as well.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.18, >=0dcac272540613d41c05e89679e4ddb978b612f1 <1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce, >=0dcac272540613d41c05e89679e4ddb978b612f1 <5d8d447777564b35f67000e7838e7ccb64d525c8, >=0dcac272540613d41c05e89679e4ddb978b612f1 <876941f533e7b47fc69977fc4551c02f2d18af97, >=0dcac272540613d41c05e89679e4ddb978b612f1 <ac48dc6ac9240f73bf08d29edf65c2deca93ee5d1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce, 5d8d447777564b35f67000e7838e7ccb64d525c8, 876941f533e7b47fc69977fc4551c02f2d18af97, ac48dc6ac9240f73bf08d29edf65c2deca93ee5d

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-35860 severity on Zeptric[![CVE-2024-35860](https://zeptric.io/badge/cve/CVE-2024-35860.svg)](https://zeptric.io/cve/CVE-2024-35860)