All reports
Medium

kernel: tracing: Fix subbuf resize races with trace_pipe_raw readers

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98032

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-19

Description

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.

A flaw was found in the Linux kernel's tracing subsystem. A race condition occurs when concurrent subbuffer resizing takes place while raw trace data is being read. A local user could exploit this flaw to cause a Denial of Service (DoS) or disclose uninitialized kernel memory due to stale buffer size values.