Linux
ring-buffer: Fix subbuf resize race with ring buffer readers
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f9b94daa542a8d2532f0930f01cd9aec2d19621b, < 6d666f0b8b36c0765cf19fbe6de5a7ba5a73aad9
- >= f9b94daa542a8d2532f0930f01cd9aec2d19621b, < 50f4a793c4ff24826efb0ac700989a5063cc53df
- >= f9b94daa542a8d2532f0930f01cd9aec2d19621b, < 0c7c517827a453128a8f58bfd849546a29813b27
- >= f9b94daa542a8d2532f0930f01cd9aec2d19621b, < 8a5f63637890f03177146efddaba5ec7a1b4d61f
Fixed in 6d666f0b8b36c0765cf19fbe6de5a7ba5a73aad9, 50f4a793c4ff24826efb0ac700989a5063cc53df, 0c7c517827a453128a8f58bfd849546a29813b27, 8a5f63637890f03177146efddaba5ec7a1b4d61f
- 6.8
Fixed in 0, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to 6d666f0b8b36c0765cf19fbe6de5a7ba5a73aad9 or 50f4a793c4ff24826efb0ac700989a5063cc53df or 0c7c517827a453128a8f58bfd849546a29813b27 or 8a5f63637890f03177146efddaba5ec7a1b4d61f or later.
Upgrade Linux to 0 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.