Linux kernel use-after-free in persistent tracing instances
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tracing: Hold trace_types_lock when updating modules in persistent instances
trace_module_record() walks ftrace_trace_arrays from the module notifier without trace_types_lock. A concurrent rmdir of an instance removes it from the list and frees it under that lock, so a module load or unload can walk into a freed trace_array.
From the CVE record · Linux
The Linux kernel's tracing code can access a freed trace_array when a module load or unload coincides with removal of a tracing instance. This race can cause a use-after-free. The input does not specify authentication requirements or whether an attacker can trigger it remotely.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.