CVE-2024-43869

Advisory lineage Upstream: 0 Downstream: 28
Modified
Published: 21 Aug 2024, 00:06
Last modified:23 May 2026, 15:53

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.01% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

21 Aug 2024, 00:06
Published
Vulnerability first disclosed
23 May 2026, 15:53
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.01%• Percentile: 2%

Techniques & Countermeasures

  • CWE-401•Missing Release of Memory after Effective Lifetime

    The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Systems

  • linux•linux

    ≥ 8bffa95ac19ff27c8261904f89d36c7fcf215d59, < 9ad46f1fef421d43cdab3a7d1744b2f43b54dae0 | ≥ 517e6a301f34613bff24a8e35b5455884f2d83d8, < ed2c202dac55423a52d7e2290f2888bf08b8ee99 | ≥ 517e6a301f34613bff24a8e35b5455884f2d83d8, < 104e258a004037bc7dba9f6085c71dad6af57ad4 | ≥ 517e6a301f34613bff24a8e35b5455884f2d83d8, < f34d8307a73a18de5320fcc6f40403146d061891 | ≥ 517e6a301f34613bff24a8e35b5455884f2d83d8, < 3a5465418f5fd970e86a86c7f4075be262682840 | 78e1317a174edbfd1182599bf76c092a2877672c | ≥ 5.15.84, < 5.15.165 | ≥ 6.0.14, < 6.1 | 6.1

  • linux•linux_kernel

    ≥ 5.15.84, < 5.15.165 | ≥ 6.0.14, < 6.1 | ≥ 6.1.1, < 6.1.103 | ≥ 6.2, < 6.6.44 | ≥ 6.7, < 6.10.3 | 6.1 | 6.1:rc8

References (6)