Local system crash via dynamic-event union confusion
Published Aug 10, 2026 · Updated Aug 10, 2026
Type confusion in Linux kernel tracing 6.14 and later allows local users to crash the system through dynamic-event module filtering. The __ftrace_set_clr_event_nolock() and update_event_fields() paths read a dynamic trace_event_call union's refcnt as call->module without checking TRACE_EVENT_FL_DYNAMIC, then dereference the integer as a module pointer. A dynamic event must have a nonzero reference count, and module-specific filtering or field updates must reach the affected path; the invalid-pointer dereference causes a kernel Oops and service interruption.
Summary
What happened
Type confusion in Linux kernel tracing 6.14 and later allows local users to crash the system through dynamic-event module filtering. The __ftrace_set_clr_event_nolock() and update_event_fields() paths read a dynamic trace_event_call union's refcnt as call->module without checking TRACE_EVENT_FL_DYNAMIC, then dereference the integer as a module pointer. A dynamic event must have a nonzero reference count, and module-specific filtering or field updates must reach the affected path; the invalid-pointer dereference causes a kernel Oops and service interruption.
The record
- CVE
- CVE-2026-68174
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-843, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=4c86bc531e60900053384867c082675bba82c29f <43a23dfe0024afd3d2b0232e987d0292919a9b24
- Affected versionversion=4c86bc531e60900053384867c082675bba82c29f <b4eb07bde606c2096b24252be589e735eff6d413
- Affected versionversion=4c86bc531e60900053384867c082675bba82c29f <b6a4575f22925da7e6aa00171e9fc0e5029c0bc9
- Affected versionversion=6.14
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.
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