Service interruption via untrusted cached kernel headers
Published Mar 10, 2024 · Updated Mar 13, 2025
Temporary-file misuse in bpftrace allows local users to interrupt service by causing BCC to load compromised Linux headers. The unpack_kheaders_tar_xz path reuses the temporary kernel-header directory when it merely exists, without verifying that root owns it. Exploitation requires low-privileged local access and header extraction; distributions that provide kernel headers are not exposed by default.
Summary
What happened
Temporary-file misuse in bpftrace allows local users to interrupt service by causing BCC to load compromised Linux headers. The unpack_kheaders_tar_xz path reuses the temporary kernel-header directory when it merely exists, without verifying that root owns it. Exploitation requires low-privileged local access and header extraction; distributions that provide kernel headers are not exposed by default.
The record
- CVE
- CVE-2024-2313
- Published
- Mar 10, 2024
- Updated
- Mar 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-377
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo