CVE-2026-74471

tracing: Check return value of __register_event() in trace_module_add_events()

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Check return value of __register_event() in trace_module_add_events() trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event. If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed. Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.10ae63b31e4d0e2ec09c569306ea46f664508ef717
Vendor states this is fixed in 000765dcdc3edf128990762790543adc4b868f6c (fixed)
Vendor states this is fixed in 22f954f7a8afe975e85517aff41b35defe05144b (fixed)
Vendor states this is fixed in 3bf965a2827c44f03294107703e7ba53fbd0a69a (fixed)
Vendor states this is fixed in 54b7a358f6399c1242d2fb7f4f96085af34baa5e (fixed)
Vendor states this is fixed in 9d6d79744f01eacaf3d5522f4fcd59939581abfd (fixed)
Vendor states this is fixed in ac8719969e6c3c54e939834df812bc41f25453cf (fixed)
Vendor states this is fixed in cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca (fixed)
Vendor states this is fixed in d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5 (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card