Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26737bpf: Fix racing between bpf_timer_cancel_and_free and bpf_timer_cancel

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26737, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected b00628b1c7d595ae5b544e059c27b1f5828314b4 – < 5268bb02107b9eedfdcd51db75b407d10043368c
    • affected b00628b1c7d595ae5b544e059c27b1f5828314b4 – < addf5e297e6cbf5341f9c07720693ca9ba0057b5
    • affected b00628b1c7d595ae5b544e059c27b1f5828314b4 – < 8327ed12e8ebc5436bfaa1786c49988894f9c8a6
    • affected b00628b1c7d595ae5b544e059c27b1f5828314b4 – < 7d80a9e745fa5b47da3bca001f186c02485c7c33
    • affected b00628b1c7d595ae5b544e059c27b1f5828314b4 – < 0281b919e175bb9c3128bd3872ac2903e9436e3f
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.80 – ≤ 6.1.*
    • unaffected 6.6.19 – ≤ 6.6.*
    • unaffected 6.7.7 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26737 badge
[![CVE-2024-26737](https://cveledger.app/badge/CVE-2024-26737.svg)](https://cveledger.app/cve/CVE-2024-26737)

Record last updated .