CVE-2024-26737

published 3 Apr 2024 · updated 5 Aug 2026

bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel

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 0281b919e175bb9c3128bd3872ac2903e9436e3f, Kernel 5268bb02107b9eedfdcd51db75b407d10043368c, Kernel 7d80a9e745fa5b47da3bca001f186c02485c7c33 and 2 more.

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel The following race is possible between bpf_timer_cancel_and_free and bpf_timer_cancel. It will lead a UAF on the timer->timer. bpf_timer_cancel(); spin_lock(); t = timer->time; spin_unlock(); bpf_timer_cancel_and_free(); spin_lock(); t = timer->timer; timer->timer = NULL; spin_unlock(); hrtimer_cancel(&t->timer); kfree(t); /* UAF on t */ hrtimer_cancel(&t->timer); In bpf_timer_cancel_and_free, this patch frees the timer->timer after a rcu grace period. This requires a rcu_head addition to the "struct bpf_hrtimer". Another kfree(t) happens in bpf_timer_init, this does not need a kfree_rcu because it is still under the spin_lock and timer->timer has not been visible by others yet. In bpf_timer_cancel, rcu_read_lock() is added because this helper can be used in a non rcu critical section context (e.g. from a sleepable bpf prog). Other timer->timer usages in helpers.c have been audited, bpf_timer_cancel() is the only place where timer->timer is used outside of the spin_lock. Another solution considered is to mark a t->flag in bpf_timer_cancel and clear it after hrtimer_cancel() is done. In bpf_timer_cancel_and_free, it busy waits for the flag to be cleared before kfree(t). This patch goes with a straight forward solution and frees timer->timer after a rcu grace period.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.15, >=b00628b1c7d595ae5b544e059c27b1f5828314b4 <0281b919e175bb9c3128bd3872ac2903e9436e3f, >=b00628b1c7d595ae5b544e059c27b1f5828314b4 <5268bb02107b9eedfdcd51db75b407d10043368c, >=b00628b1c7d595ae5b544e059c27b1f5828314b4 <7d80a9e745fa5b47da3bca001f186c02485c7c33, >=b00628b1c7d595ae5b544e059c27b1f5828314b4 <8327ed12e8ebc5436bfaa1786c49988894f9c8a6, >=b00628b1c7d595ae5b544e059c27b1f5828314b4 <addf5e297e6cbf5341f9c07720693ca9ba0057b50281b919e175bb9c3128bd3872ac2903e9436e3f, 5268bb02107b9eedfdcd51db75b407d10043368c, 7d80a9e745fa5b47da3bca001f186c02485c7c33, 8327ed12e8ebc5436bfaa1786c49988894f9c8a6, addf5e297e6cbf5341f9c07720693ca9ba0057b5

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-26737 severity on Zeptric[![CVE-2024-26737](https://zeptric.io/badge/cve/CVE-2024-26737.svg)](https://zeptric.io/cve/CVE-2024-26737)