CVE-2024-43869
MediumIn 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 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness type
CWE-401CVE-2024-43869 is a Memory Leak vulnerability
What is Memory Leak?
The product does not release memory after use, causing gradual resource exhaustion. Learn more on MITRE CWE
Affected versions
Linux kernel versions
5.15.84,
6.0.14,
6.1
and later are affected. Fixed in
5.15.165,
6.1.103,
6.6.44,
6.10.3,
6.11
and their respective stable series.
References
The following references provide additional information about CVE-2024-43869 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
-
PatchKernel patch commithttps://git.kernel.org/stable/c/104e258a004037bc7dba9f6085c71dad6af57ad4
-
PatchKernel patch commithttps://git.kernel.org/stable/c/3a5465418f5fd970e86a86c7f4075be262682840
-
PatchKernel patch commithttps://git.kernel.org/stable/c/9ad46f1fef421d43cdab3a7d1744b2f43b54dae0
Frequently asked questions
-
What is CVE-2024-43869?
CVE-2024-43869 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Memory Leak flaw (CWE-401) . It affects Linux kernel versions from 5.15.84 onward and has been patched in 5.15.165, 6.1.103, 6.6.44 and others. CVE-2024-43869 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2024-43869?
CVE-2024-43869 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2024-43869?
Yes — CVE-2024-43869 has been patched. Fixed versions include 5.15.165, 6.1.103, 6.6.44 and others. If you are running Linux kernel 5.15.84 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2024-43869 actively exploited?
No — CVE-2024-43869 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
-
What is Memory Leak (CWE-401)?
The product does not release memory after use, causing gradual resource exhaustion. View CWE-401 on MITRE CWE →