CVE-2024-41045
bpf: Defer work in bpf_timer_cancel_and_free
Reported by linux · Published July 29, 2024
In the Linux kernel, the following vulnerability has been resolved: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.9.10 |
| Linux | Linux | a6fcd19d7eac1335eb76bc16b6a66b7f574d1d69 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | b00628b1c7d595ae5b544e059c27b1f5828314b4, b00628b1c7d595ae5b544e059c27b1f5828314b4, b00628b1c7d595ae5b544e059c27b1f5828314b4 |
| Linux | Linux | 5.15, 0, 6.1.191 |
| Linux | Linux | 6.10, 0, 6.1.191 |
| linux | linux_kernel | 5.15, 5.15, 5.15 |
Timeline
- Jul 29, 2024 CVE Published
- Jul 30, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (15 in total, the first dated here)
- Jan 7, 2026 Security Advisory (355 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (237 in total, the first dated here)
- Oct 30, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-41045
vulnetix vdb fixes CVE-2024-41045
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-41045/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart