ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
In rb_allocate_cpu_buffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGE_SIZE if when freed: free_buffer_page() relies on this value. Align the value with the actual allocation size (buffer::subbuf_order).
From the CVE record · Linux
The Linux kernel ring-buffer leaves the reader page order set to zero instead of the allocation order. This can cause incorrect page freeing when a ring-buffer with sub-buffers larger than PAGE_SIZE is freed. The input does not describe an attacker action, access requirements, or user interaction.
Engineers running the Linux kernel should check whether their version includes this ring-buffer fix; affected versions are not specified.