CVE-2026-74602: ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Initialise reader page order in rballocatecpubuffer()
In rballocatecpubuffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGESIZE if when freed: freebufferpage() relies on this value. Align the value with the actual allocation size (buffer::subbuforder).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In rb_allocate_cpu_buffer(), initialize reader page order (bpage->order) using buffer::subbuf_order instead of leaving it as 0, so that free_buffer_page() uses the correct allocation size.
Linux kernel ring-buffer bpage->order = buffer::subbuf_order