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.
https://git.kernel.org/stable/c/e70f5ee4c8824736332351b703c46f9469ed7f6c
https://git.kernel.org/stable/c/db45632479ceecb669612ed8dbce927e3c6279fc
https://git.kernel.org/stable/c/ca60064ea03f14e06c763de018403cb56ba3207d
https://git.kernel.org/stable/c/b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df
https://git.kernel.org/stable/c/7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b
https://git.kernel.org/stable/c/70fecd519caad0c1741c3379d5348c9000a5b29d
https://git.kernel.org/stable/c/6bc94f20a4c304997288f9a45278c9d0c06987d3
https://git.kernel.org/stable/c/33e20747b47ddc03569b6bc27a2d6894c1428182