tracing: Fix subbuf resize races with trace_pipe_raw readers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.114, 6.18.57, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 574efd988d116bd56ac688ab2d64e06ba0da982a; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 3f30b2cd4eba45c05f822f03f1b0f4077d6d4dc3; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 75b37b8369778b69ce9738d1c97685a1615cb252; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in dae8dda341d2d9034a90d59e8a7d502e1263813f
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.7