tracing: Check return value of __register_event() in trace_module_add_events()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae63b31e4d0e2ec09c569306ea46f664508ef717 · < cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Linux kernel tracing can retain a stale event pointer if event registration and subsequent module loading fail. Later tracefs or tracing operations can trigger a use-after-free. The input does not specify attacker access requirements or whether user interaction is needed.
Teams running Linux kernels should check whether their builds include the affected tracing code; affected versions are not specified.