CVE-2026-68174: tracing: Fix union collision of module and refcnt for dynamic events

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

tracing: Fix union collision of module and refcnt for dynamic events

In 'struct traceeventcall', 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 'setevent'), the code in 'ftracesetclreventnolock()' and 'updateeventfields()' 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 'TRACEEVENTFLDYNAMIC' flag is checked before treating 'call->module' as a valid pointer in these code paths.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Ensure that the TRACE_EVENT_FL_DYNAMIC flag is checked before treating call->module as a valid pointer in the tracing code paths that call __ftrace_set_clr_event_nolock() and update_event_fields() for dynamic events.

    Linux kernel tracing (trace_event_call / dynamic events) TRACE_EVENT_FL_DYNAMIC flag check before using call->module = enabled

Event History

Aug 10, 2026
CVE Published
via MITRE·11:59 AM
Data Sourced
via MITRE·11:59 AM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68174?

CVE-2026-68174 has a risk score of 37, indicating potential moderate impact.

2

How do I fix CVE-2026-68174?

To resolve CVE-2026-68174, update to the latest version of the Linux kernel where the vulnerability has been patched.

3

What is CVE-2026-68174 concerning?

CVE-2026-68174 addresses a union collision issue in the Linux kernel's tracing subsystem related to dynamic events.

4

Which software is affected by CVE-2026-68174?

CVE-2026-68174 affects the Linux kernel.

5

Can CVE-2026-68174 lead to security risks?

Yes, CVE-2026-68174 may lead to security risks given its potential impact on dynamic events in the kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203