The Linux kernel ring-buffer had a flaw in the rb_allocate_cpu_buffer() function where the bpage->order field was not initialized correctly, remaining zero. This omission affects ring-buffers with sub-buffers larger than PAGE_SIZE because the free_buffer_page() function relies on the order value to free memory correctly. The vulnerability was addressed by initializing bpage->order to match the buffer's subbuf_order, ensuring proper memory management and preventing potential errors during buffer page freeing.

Incorrect initialization of the reader page order could lead to improper memory management when freeing buffer pages in the ring-buffer subsystem. This may cause stability or reliability issues in the kernel, particularly for ring-buffers with sub-buffers larger than a page size. No direct exploit or active attacks are known, and no CVSS score is assigned.

A fix has been applied in the Linux kernel to initialize the reader page order correctly in rb_allocate_cpu_buffer(). Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the exact fixed versions and apply updates accordingly.