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-43869perf: Fix event leak upon exec and file release

Description

In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exec and file release The perf pending task work is never waited upon the matching event release. In the case of a child event, released via free_event() directly, this can potentially result in a leaked event, such as in the following scenario that doesn't even require a weak IRQ work implementation to trigger: schedule() prepare_task_switch() =======> <NMI> perf_event_overflow() event->pending_sigtrap = ... irq_work_queue(&event->pending_irq) <======= </NMI> perf_event_task_sched_out() event_sched_out() event->pending_sigtrap = 0; atomic_long_inc_not_zero(&event->refcount) task_work_add(&event->pending_task) finish_lock_switch() =======> <IRQ> perf_pending_irq() //do nothing, rely on pending task work <======= </IRQ> begin_new_exec() perf_event_exit_task() perf_event_exit_event() // If is child event free_event() WARN(atomic_long_cmpxchg(&event->refcount, 1, 0) != 1) // event is leaked Similar scenarios can also happen with perf_event_remove_on_exec() or simply against concurrent perf_event_release(). Fix this with synchonizing against the possibly remaining pending task work while freeing the event, just like is done with remaining pending IRQ work. This means that the pending task callback neither need nor should hold a reference to the event, preventing it from ever beeing freed.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 21 months 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-43869, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (12 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 8bffa95ac19ff27c8261904f89d36c7fcf215d59 – < 9ad46f1fef421d43cdab3a7d1744b2f43b54dae0
    • affected 517e6a301f34613bff24a8e35b5455884f2d83d8 – < ed2c202dac55423a52d7e2290f2888bf08b8ee99
    • affected 517e6a301f34613bff24a8e35b5455884f2d83d8 – < 104e258a004037bc7dba9f6085c71dad6af57ad4
    • affected 517e6a301f34613bff24a8e35b5455884f2d83d8 – < f34d8307a73a18de5320fcc6f40403146d061891
    • affected 517e6a301f34613bff24a8e35b5455884f2d83d8 – < 3a5465418f5fd970e86a86c7f4075be262682840
    • affected 78e1317a174edbfd1182599bf76c092a2877672c
    • affected 5.15.84 – < 5.15.165
    • affected 6.0.14 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.103 – ≤ 6.1.*
    • unaffected 6.6.44 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .