CVE-2026-68174
N/A
Summary
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix union collision of module and refcnt for dynamic events
In 'struct trace_event_call', the 'module' pointer and the 'refcnt' atomic variable share the same memory space in a union. For dynamic events, the union member is 'refcnt', which acts as an active reference counter.
When a dynamic event (such as kprobe, uprobe, fprobe, eprobe, or wprobe) has a non-zero reference count (e.g. due to active event triggers or perf attachments), its 'call->module' evaluates to a small non-zero integer instead of NULL.
When filtering or setting events for a specific module (e.g., writing ':mod:<module>' to 'set_event'), the code in '__ftrace_set_clr_event_nolock()' and 'update_event_fields()' reads 'call->module' directly without checking whether the event is dynamic. This causes the kernel to treat the small integer (refcnt) as a 'struct module' pointer, leading to a NULL/invalid pointer dereference (Oops) when dereferencing the module name.
Fix this by ensuring that the 'TRACE_EVENT_FL_DYNAMIC' flag is checked before treating 'call->module' as a valid pointer in these code paths.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 4c86bc531e60900053384867c082675bba82c29f < b6a4575f22925da7e6aa00171e9fc0e5029c0bc9 | affected |
| Linux | Linux | 4c86bc531e60900053384867c082675bba82c29f < 43a23dfe0024afd3d2b0232e987d0292919a9b24 | affected |
| Linux | Linux | 4c86bc531e60900053384867c082675bba82c29f < b4eb07bde606c2096b24252be589e735eff6d413 | affected |
| Linux | Linux | 6.14 | affected |
| Linux | Linux | 0 < 6.14 | unaffected |
| Linux | Linux | 6.18.42 <= 6.18.* | unaffected |
| Linux | Linux | 7.1.6 <= 7.1.* | unaffected |
| Linux | Linux | 7.2-rc5 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/b6a4575f22925da7e6aa00171e9fc0e5029c0bc9
- https://git.kernel.org/stable/c/43a23dfe0024afd3d2b0232e987d0292919a9b24
- https://git.kernel.org/stable/c/b4eb07bde606c2096b24252be589e735eff6d413
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.