https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 10:16:23 +0000 https://cve.radiocsirt.org/vuln/cve-2026-89503 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()</p> <p>ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn&#39;t a big issue, the user can still re-allocate a new reader page and try again.</p> <p>However, what is more problematic is if the value of subbuf_order changes in the middle of ring_buffer_alloc_read_page(). In that case, bpage-&gt;order might not match the actual allocated memory.</p> <p>Use bpage-&gt;order for the allocation to prevent this race.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()</p> <p>ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn&#39;t a big issue, the user can still re-allocate a new reader page and try again.</p> <p>However, what is more problematic is if the value of subbuf_order changes in the middle of ring_buffer_alloc_read_page(). In that case, bpage-&gt;order might not match the actual allocated memory.</p> <p>Use bpage-&gt;order for the allocation to prevent this race.</p> https://cve.radiocsirt.org/vuln/cve-2026-89503