CVE-2025-68186

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up<br /> <br /> The function ring_buffer_map_get_reader() is a bit more strict than the<br /> other get reader functions, and except for certain situations the<br /> rb_get_reader_page() should not return NULL. If it does, it triggers a<br /> warning.<br /> <br /> This warning was triggering but after looking at why, it was because<br /> another acceptable situation was happening and it wasn&amp;#39;t checked for.<br /> <br /> If the reader catches up to the writer and there&amp;#39;s still data to be read<br /> on the reader page, then the rb_get_reader_page() will return NULL as<br /> there&amp;#39;s no new page to get.<br /> <br /> In this situation, the reader page should not be updated and no warning<br /> should trigger.