Kernel crash via dangling trace_event_file reference
Published May 21, 2024 · Updated Aug 5, 2026
Use-after-free in Linux kernel tracing allows local users to crash the kernel through crafted tracefs kprobe event operations. Deleting an event frees its trace_event_file while an open enable file retains a reference, so a later write or close dereferences freed memory. Local access and permission to modify tracefs kprobe events are required; closing the retained descriptor can trigger a kernel oops.
Summary
What happened
Use-after-free in Linux kernel tracing allows local users to crash the kernel through crafted tracefs kprobe event operations. Deleting an event frees its trace_event_file while an open enable file retains a reference, so a later write or close dereferences freed memory. Local access and permission to modify tracefs kprobe events are required; closing the retained descriptor can trigger a kernel oops.
The record
- CVE
- CVE-2023-52879
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=407bf1c140f0757706c0b28604bcc90837d45ce2 <a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f
- Affected versionversion=5.10.198 <5.10.202
- Affected versionversion=5.15.134 <5.15.140
- Affected versionversion=5.4.258 <5.4.262
- Affected versionversion=6.1.55 <6.1.64
- Affected versionversion=6.5.5 <6.5.13
- Affected versionversion=6.6
- Affected versionversion=9beec04370132a7a6cd1aa9897f6fffc6262ff28 <2c9de867ca285c397cd71af703763fe416265706
- Affected versionversion=a46bf337a20f9edd3c8041b025639842280d0575 <2fa74d29fc1899c237d51bf9a6e132ea5c488976
- Affected versionversion=e6807c873d8791ae5a5186ad05ec66cab926539a <961c4511c7578d6b8f39118be919016ec3db1c1e
- Affected versionversion=f5ca233e2e66dc1c249bf07eefa37e34a6c9346a <9034c87d61be8cff989017740a91701ac8195a1d
- Affected versionversion=f5ca233e2e66dc1c249bf07eefa37e34a6c9346a <bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4
- Affected versionversion=fa6d449e4d024d8c17f4288e0567d28ace69415c <cbc7c29dff0fa18162f2a3889d82eeefd67305e0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- Linux kernel tracefs kprobe reproducerproof of concept · demonstrated
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