CVE-2024-43869

published 21 Aug 2024 · updated 17 Nov 2026

perf: Fix event leak upon exec and file release

5.0MediumEPSS 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 9ad46f1fef421d43cdab3a7d1744b2f43b54dae0, Kernel 104e258a004037bc7dba9f6085c71dad6af57ad4, Kernel 3a5465418f5fd970e86a86c7f4075be262682840 and 7 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=8bffa95ac19ff27c8261904f89d36c7fcf215d59 <9ad46f1fef421d43cdab3a7d1744b2f43b54dae0, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <104e258a004037bc7dba9f6085c71dad6af57ad4, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <3a5465418f5fd970e86a86c7f4075be262682840, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <ed2c202dac55423a52d7e2290f2888bf08b8ee99, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <f34d8307a73a18de5320fcc6f40403146d061891, >=6.0.14 <6.1, =6.1, =78e1317a174edbfd1182599bf76c092a2877672c, >=5.15.84 <5.15.1659ad46f1fef421d43cdab3a7d1744b2f43b54dae0, 104e258a004037bc7dba9f6085c71dad6af57ad4, 3a5465418f5fd970e86a86c7f4075be262682840, ed2c202dac55423a52d7e2290f2888bf08b8ee99, f34d8307a73a18de5320fcc6f40403146d061891, 6.1, 5.15.165
linux-kernel: Kernel>=6.0.14 <6.1, >=6.1.0 <6.1.103, >=6.2.0 <6.6.44, >=6.7.0 <6.10.3, >=5.15.84 <5.15.1656.1, 6.1.103, 6.6.44, 6.10.3, 5.15.165

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