CVE-2024-43870

published 21 Aug 2024 · updated 17 Nov 2026

perf: Fix event leak upon exit

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 67fad724f1b568b356c1065d50df46e6b30eb2f7, Kernel 05d3fd599594abf79aad4484bccb2b26e1cb0b51, Kernel 2fd5ad3f310de22836cdacae919dd99d758a1f1b and 7 more.

In the Linux kernel, the following vulnerability has been resolved: perf: Fix event leak upon exit When a task is scheduled out, pending sigtrap deliveries are deferred to the target task upon resume to userspace via task_work. However failures while adding an event's callback to the task_work engine are ignored. And since the last call for events exit happen after task work is eventually closed, there is a small window during which pending sigtrap can be queued though ignored, leaking the event refcount addition such as in the following scenario: TASK A ----- do_exit() exit_task_work(tsk); <IRQ> perf_event_overflow() event->pending_sigtrap = pending_id; irq_work_queue(&event->pending_irq); </IRQ> =========> PREEMPTION: TASK A -> TASK B event_sched_out() event->pending_sigtrap = 0; atomic_long_inc_not_zero(&event->refcount) // FAILS: task work has exited task_work_add(&event->pending_task) [...] <IRQ WORK> perf_pending_irq() // early return: event->oncpu = -1 </IRQ WORK> [...] =========> TASK B -> TASK A perf_event_exit_task(tsk) perf_event_exit_event() free_event() WARN(atomic_long_cmpxchg(&event->refcount, 1, 0) != 1) // leak event due to unexpected refcount == 2 As a result the event is never released while the task exits. Fix this with appropriate task_work_add()'s error handling.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=8bffa95ac19ff27c8261904f89d36c7fcf215d59 <67fad724f1b568b356c1065d50df46e6b30eb2f7, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <05d3fd599594abf79aad4484bccb2b26e1cb0b51, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <2fd5ad3f310de22836cdacae919dd99d758a1f1b, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a, >=517e6a301f34613bff24a8e35b5455884f2d83d8 <70882d7fa74f0731492a0d493e8515a4f7131831, >=6.0.14 <6.1, =6.1, =78e1317a174edbfd1182599bf76c092a2877672c, >=5.15.84 <5.15.16567fad724f1b568b356c1065d50df46e6b30eb2f7, 05d3fd599594abf79aad4484bccb2b26e1cb0b51, 2fd5ad3f310de22836cdacae919dd99d758a1f1b, 3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a, 70882d7fa74f0731492a0d493e8515a4f7131831, 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-43870 severity on Zeptric[![CVE-2024-43870](https://zeptric.io/badge/cve/CVE-2024-43870.svg)](https://zeptric.io/cve/CVE-2024-43870)