Local system crash via invalid tracing cleanup
Published Jul 19, 2026 · Updated Jul 19, 2026
Memory corruption in the Linux Kernel tracing subsystem allows local users to crash the system through a tracing map allocation failure. In tracing_map_elt_alloc(), an error path calls map->ops->elt_free() after map->ops->elt_alloc() fails, freeing client data that was never initialized. Exploitation requires local low-privileged access and an allocation failure; the bounded consequence is system instability or denial of service.
Summary
What happened
Memory corruption in the Linux Kernel tracing subsystem allows local users to crash the system through a tracing map allocation failure. In tracing_map_elt_alloc(), an error path calls map->ops->elt_free() after map->ops->elt_alloc() fails, freeing client data that was never initialized. Exploitation requires local low-privileged access and an allocation failure; the bounded consequence is system instability or denial of service.
The record
- CVE
- CVE-2026-64173
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-1341, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=2734b629525a9dae5bf217cbf0a9651da93d2108 <1a150947f8480262a46c860f1acb9c6597ca7097
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <49332e49ad5b20262cc719b03d4123b9362de701
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <798183376d9d3e278a270ea0e75a5769c8f145d9
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <8f0f5c4fb9df0e19a341e0c6ed8dc4fda9124f03
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <b427e9f6d81c9341cba23ef92f860f99f830d91d
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <b559a218eece132de0c58d444877b5627cbee524
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <b6723339736320b2e1784258ad4490cec7aac11a
- Affected versionversion=2734b629525a9dae5bf217cbf0a9651da93d2108 <f383cff9fb382139980bac1bcd3f3f5d59f68435
- Affected versionversion=4.17
What conditions does exploitation require?
What is affected?
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