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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-43870 is a Linux kernel perf bug where a task exit race can leave a performance event reference unreleased. The described impact is a resource leak during process exit, not confirmed remote code execution or privilege escalation. Treat it as kernel maintenance risk unless your environment depends heavily on affected Linux kernels.
Executive priority
Handle through normal kernel patch management, with higher priority for exposed production fleets and multi-tenant Linux hosts. Current evidence supports operational risk from resource leakage, not emergency response for active exploitation.
Technical view
The perf subsystem may ignore task_work_add() failure after task work has closed during task exit. A pending sigtrap path can increment an event refcount, fail to queue cleanup, then leave free_event() seeing an unexpected refcount. The fix adds task_work_add() error handling.
Likely exposure
Exposure is Linux systems running affected kernel versions or distro backports identified by vendors. The source bundle lists upstream Linux as affected for several 5.15, 6.1, 6.6, 6.10, and 6.11-related versions, but package-level status must be confirmed by each distributor.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, exploit code, or a CVSS score. The described scenario requires a narrow kernel race involving perf event overflow, pending sigtrap handling, task scheduling, and task exit.
Researcher notes
Evidence is limited to the kernel CVE description, stable commit references, and a Debian LTS advisory link. The root issue is missed error handling in perf task_work cleanup during a task exit race. No source names affected distributions beyond Debian LTS context.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Check distributor advisories before relying on upstream version numbers.
Review the Debian LTS announcement if running Debian LTS.
Prioritize shared or long-running Linux hosts where kernel leaks are operationally costly.
Track exceptions until an updated kernel package is installed.
Validation and detection
Inventory running kernel versions across Linux hosts.
Compare package status with vendor advisories for CVE-2024-43870.
Verify kernel changelogs include this CVE or referenced stable commits.
Confirm rebooted systems are running the updated kernel.
Document remaining affected hosts and planned update windows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-43870 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.