CVE-2024-43869
Last modified
CVE-2024-43869 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15.84, < 5.15.165 |
| Linux | Linux Kernel | >= 6.0.14, < 6.1 |
| Linux | Linux Kernel | >= 6.1.1, < 6.1.103 |
| Linux | Linux Kernel | >= 6.2, < 6.6.44 |
| Linux | Linux Kernel | >= 6.7, < 6.10.3 |
| Linux | Linux Kernel | 6.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-43869?
How severe is CVE-2024-43869?
How do I fix CVE-2024-43869?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-43863In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43864In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43865In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43866In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-43867In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43868In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4387Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-43870In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43871In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43872In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-43873In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-43874In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-43869?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
