<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 09:33:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68186 — ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68186</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up&lt;/p&gt;
&lt;p&gt;The function ring_buffer_map_get_reader() is a bit more strict than the
other get reader functions, and except for certain situations the
rb_get_reader_page() should not return NULL. If it does, it triggers a
warning.&lt;/p&gt;
&lt;p&gt;This warning was triggering but after looking at why, it was because
another acceptable situation was happening and it wasn&amp;#39;t checked for.&lt;/p&gt;
&lt;p&gt;If the reader catches up to the writer and there&amp;#39;s still data to be read
on the reader page, then the rb_get_reader_page() will return NULL as
there&amp;#39;s no new page to get.&lt;/p&gt;
&lt;p&gt;In this situation, the reader page should not be updated and no warning
should trigger.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up&lt;/p&gt;
&lt;p&gt;The function ring_buffer_map_get_reader() is a bit more strict than the
other get reader functions, and except for certain situations the
rb_get_reader_page() should not return NULL. If it does, it triggers a
warning.&lt;/p&gt;
&lt;p&gt;This warning was triggering but after looking at why, it was because
another acceptable situation was happening and it wasn&amp;#39;t checked for.&lt;/p&gt;
&lt;p&gt;If the reader catches up to the writer and there&amp;#39;s still data to be read
on the reader page, then the rb_get_reader_page() will return NULL as
there&amp;#39;s no new page to get.&lt;/p&gt;
&lt;p&gt;In this situation, the reader page should not be updated and no warning
should trigger.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68186</guid>
    </item>
  </channel>
</rss>
