Linux kernel double-free in last-boot tracing data
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 resetting last boot data from readers
update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and tracing_buffers_read() without trace_types_lock. Two readers can both pass the LAST_BOOT test and free module_delta twice, and a module notifier can update module_delta while it is being freed.
Take trace_types_lock in those paths and keep the callers that already hold it on an unlocked variant.
From the CVE record · Linux
The Linux kernel tracing code can reset last-boot data without holding trace_types_lock. Concurrent readers can free module_delta twice, or a module notifier can update it while it is being freed. The issue requires concurrent access to the affected tracing paths; the input does not specify authentication requirements.
Engineers running Linux kernels with the affected tracing code should check their versions against the vendor advisory; affected versions are not specified.