tracing: Fix subbuf resize races with trace_pipe_raw readers
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: Fix subbuf resize races with trace_pipe_raw readers
Concurrent subbuffer resizes may crash trace_pipe_raw readers or leak uninitialized memory to userspace due to stale size values.
Modify ring_buffer_alloc_read_page() to handle the resizing of an existing buffer_data_read_page if necessary and add a new ring_buffer_read_page_size(). This new function enables ring-buffer buffer_data_read_page users to not call the racy ring_buffer_subbuf_size_get(). This makes the spare_size member of ftrace_buffer_info redundant.
Finally, handle buffer_data_read_page/reader_page order discrepancy in ring_buffer_read_page(). On a mismatch simply copy manually the data to the buffer_data_read_page.
From the CVE record · Linux
Concurrent subbuffer resizes in the Linux kernel tracing ring buffer can cause trace_pipe_raw readers to crash or receive uninitialized memory. This requires a resize while a trace_pipe_raw reader is active; the input does not specify authentication requirements.
Operators running Linux kernels with trace_pipe_raw readers should check whether their kernel includes the tracing fix; affected versions were not specified.