ring-buffer: Fix subbuf resize race with ring buffer readers

Summary

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring buffer readers trace_buffer subbuf_size is read lockless in ring_buffer_read_page() and ring_buffer_read_start(), while it can simultaneously be resized with ring_buffer_subbuf_order_set(). Instead of trace_buffer::subbuf_size, use bpage::order in ring_buffer_read_start() and ring_buffer_read_page(). In ring_buffer_read_start(), even with resize_disabled, there is still a possibility of a race with a buffer modification. Hold the trace_buffer mutex to synchronise with any pending ring buffer order modification. trace_buffer::subbuf_size is now actually useless, remove it. Also, create accessors rb_subbuf_capacity() and rb_page_capacity() which return the actual size available for storing events, while rb_subbuf_size() returns the actual subbuf page-size.

Timeline

1. Sep 11, 2026, 7:47 PM UTCCVE published
2. Oct 19, 2026, 8:52 AM UTCRecord last updated

Affected versions

• Linux Linux

  From f9b94daa542a8d2532f0930f01cd9aec2d19621b · fixed in 6d666f0b8b36c0765cf19fbe6de5a7ba5a73aad9; From f9b94daa542a8d2532f0930f01cd9aec2d19621b · fixed in 50f4a793c4ff24826efb0ac700989a5063cc53df; From f9b94daa542a8d2532f0930f01cd9aec2d19621b · fixed in 0c7c517827a453128a8f58bfd849546a29813b27; From f9b94daa542a8d2532f0930f01cd9aec2d19621b · fixed in 8a5f63637890f03177146efddaba5ec7a1b4d61f

• Linux Linux

  6.8

• KernelLinux

  From 6.8.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4

References 4