tracing: Add down_write(trace_event_sem) when adding trace event
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 110bf2b764eb6026b868d84499263cb24b1bcc8d · < 33e20747b47ddc03569b6bc27a2d6894c1428182| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tracing: Add down_write(trace_event_sem) when adding trace event
When a module is loaded, it adds trace events defined by the module. It may also need to modify the modules trace printk formats to replace enum names with their values.
If two modules are loaded at the same time, the adding of the event to the ftrace_events list can corrupt the walking of the list in the code that is modifying the printk format strings and crash the kernel.
The addition of the event should take the trace_event_sem for write while it adds the new event.
Also add a lockdep_assert_held() on that semaphore in __trace_add_event_dirs() as it iterates the list.
From the CVE record · Linux
The Linux kernel’s tracing code can corrupt an event list when two modules load at the same time. This can crash the kernel; the input does not specify whether an attacker needs authentication or user interaction to trigger the module loads.
Engineers running Linux kernels with module tracing should check their versions; affected versions are not specified.