https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 29 Oct 2026 13:30:51 +0000 https://db.gcve.eu/vuln/cve-2026-99158 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Fix false warning in ring_buffer_map_get_reader()</p> <p>The mmap reader can warn when it catches up with a writer that is still committing events. rb_get_reader_page() returns NULL in this case, but ring_buffer_map_get_reader() treats that result as an error.</p> <p>The initial rb_per_cpu_empty() check filters out an empty buffer, but it does not guarantee that the next reader page has committed data. Writers do not take reader_lock and can advance commit_page before publishing the committed length on the new page. rb_get_reader_page() can swap to that page, catch up with the writer and return NULL.</p> <p>Handle NULL through the existing no-data exit without warning. Remove the caller&#39;s reader_page == commit_page check as well, since the reader-page helper already handles that case. The existing metadata update and return path remain in place.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Fix false warning in ring_buffer_map_get_reader()</p> <p>The mmap reader can warn when it catches up with a writer that is still committing events. rb_get_reader_page() returns NULL in this case, but ring_buffer_map_get_reader() treats that result as an error.</p> <p>The initial rb_per_cpu_empty() check filters out an empty buffer, but it does not guarantee that the next reader page has committed data. Writers do not take reader_lock and can advance commit_page before publishing the committed length on the new page. rb_get_reader_page() can swap to that page, catch up with the writer and return NULL.</p> <p>Handle NULL through the existing no-data exit without warning. Remove the caller&#39;s reader_page == commit_page check as well, since the reader-page helper already handles that case. The existing metadata update and return path remain in place.</p> https://db.gcve.eu/vuln/cve-2026-99158