Description
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Make cpu_buffer::free_page a buffer_data_read_page Discarding a cached reader page after a concurrent ring buffer resize uses the new global subbuf_order for the free_pages() call. This mismatched order may crashes the kernel or leaks memory because the cached page was allocated under the old size. Save the actual free_page order alongside the page address to ensure we always refer to the correct value and do not rely on the potentially stalled cpu_buffer->subbuf_order value. The simplest is to make free_page a buffer_data_read_page which already covers exactly what we need: a page address and a page order.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
8e7b58c27b3c567316a51079b375b846f9223bba to < d8f52dc3c3f1f987d8cf920ccd8d66590870bf3faffected8e7b58c27b3c567316a51079b375b846f9223bba to < a1dabe68fb53730bc0be60c5dbfd3f4c560084e7affected8e7b58c27b3c567316a51079b375b846f9223bba to < d787d509bdf6c88c85e095247daf7456cb7fb772affected8e7b58c27b3c567316a51079b375b846f9223bba to < 7a1fb95de5404134f8758c1295ce88986bdf117caffected
Linux Linux
Default version status: affected
6.8affected0 to < 6.8unaffected6.12.112 to ≤ 6.12.*unaffected6.18.51 to ≤ 6.18.*unaffected7.2.4 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected