CVE-2024-43870: perf: Fix event leak upon exit
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 05d3fd599594abf79aad4484bccb2b26e1cb0b51, 2fd5ad3f310de22836cdacae919dd99d758a1f1b, 3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 05d3fd599594abf79aad4484bccb2b26e1cb0b51, 2fd5ad3f310de22836cdacae919dd99d758a1f1b, 3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.84 and later · before 5.15.165
- linux linux kernel6.0.14 and later · before 6.1
- linux linux kernel6.1.1 and later · before 6.1.103
- linux linux kernel6.2 and later · before 6.6.44
- linux linux kernel6.7 and later · before 6.10.3
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 78e1317a174edbfd1182599bf76c092a2877672c, 6.1affected
- 8bffa95ac19ff27c8261904f89d36c7fcf215d59 and later · before 67fad724f1b568b356c1065d50df46e6b30eb2f7affected · git
- 517e6a301f34613bff24a8e35b5455884f2d83d8 and later · before 70882d7fa74f0731492a0d493e8515a4f7131831affected · git
- 517e6a301f34613bff24a8e35b5455884f2d83d8 and later · before 05d3fd599594abf79aad4484bccb2b26e1cb0b51affected · git
- 517e6a301f34613bff24a8e35b5455884f2d83d8 and later · before 3d7a63352a93bdb8a1cdf29606bf617d3ac1c22aaffected · git
- 517e6a301f34613bff24a8e35b5455884f2d83d8 and later · before 2fd5ad3f310de22836cdacae919dd99d758a1f1baffected · git
- 5.15.84 and later · before 5.15.165affected · semver
- 6.0.14 and later · before 6.1affected · semver
- before 6.1not affected · semver
- 5.15.165 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.10.3-1 | 6.10.3-1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-coco | before 6.4.0-15061.6.coco15sp6.1 | 6.4.0-15061.6.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-coco_debug | before 6.4.0-15061.6.coco15sp6.1 | 6.4.0-15061.6.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-source-coco | before 6.4.0-15061.6.coco15sp6.1 | 6.4.0-15061.6.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-syms-coco | before 6.4.0-15061.6.coco15sp6.1 | 6.4.0-15061.6.coco15sp6.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-43868Aug 20, 2024 · riscv/purgatory: align riscv_kernel_entry22Monitor
- ← EarlierCVE-2024-43869Aug 20, 2024 · perf: Fix event leak upon exec and file release22Monitor
- Later →CVE-2024-43873Aug 20, 2024 · vhost/vsock: always initialize seqpacket_allow31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 05d3fd599594abf79aad4484bccb2b26e1cb0b51 | Vendor (CNA) |
| Linux Linux | 2fd5ad3f310de22836cdacae919dd99d758a1f1b | Vendor (CNA) |
| Linux Linux | 3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a | Vendor (CNA) |
| Linux Linux | 5.15.165 | Vendor (CNA) |
| Linux Linux | 6.1 | Vendor (CNA) |
| Linux Linux | 67fad724f1b568b356c1065d50df46e6b30eb2f7 | Vendor (CNA) |
| Linux Linux | 70882d7fa74f0731492a0d493e8515a4f7131831 | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-coco | 6.4.0-15061.6.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-coco_debug | 6.4.0-15061.6.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-source-coco | 6.4.0-15061.6.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-coco | 6.4.0-15061.6.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1309 · Aug 21, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2fd5ad3f310de22836cdacae919dd99d758a1f1b
- git.kernel.org/stable/c/3d7a63352a93bdb8a1cdf29606bf617d3ac1c22a
- git.kernel.org/stable/c/67fad724f1b568b356c1065d50df46e6b30eb2f7
- git.kernel.org/stable/c/70882d7fa74f0731492a0d493e8515a4f7131831
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.