Tracker / CVE-2025-38539
CVE-2025-38539
High 7.8
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.
Affected products and versions
| debian | debian_linux |
|---|---|
| linux | linux_kernel |
| linux | linux_kernel · 2.6.31 → 5.4.297 |
| linux | linux_kernel · 5.11 → 5.15.190 |
| linux | linux_kernel · 5.16 → 6.1.147 |
| linux | linux_kernel · 5.5 → 5.10.241 |
| linux | linux_kernel · 6.13 → 6.15.8 |
| linux | linux_kernel · 6.2 → 6.6.100 |
| linux | linux_kernel · 6.7 → 6.12.40 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.