<?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>Thu, 01 Oct 2026 15:12:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46234 — vsock: fix buffer size clamping order</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46234</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;vsock: fix buffer size clamping order&lt;/p&gt;
&lt;p&gt;In vsock_update_buffer_size(), the buffer size was being clamped to the
maximum first, and then to the minimum. If a user sets a minimum buffer
size larger than the maximum, the minimum check overrides the maximum
check, inverting the constraint.&lt;/p&gt;
&lt;p&gt;This breaks the intended socket memory boundaries by allowing the
vsk-&amp;gt;buffer_size to grow beyond the configured vsk-&amp;gt;buffer_max_size.&lt;/p&gt;
&lt;p&gt;Fix this by checking the minimum first, and then the maximum. This
ensures the buffer size never exceeds the buffer_max_size.&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;vsock: fix buffer size clamping order&lt;/p&gt;
&lt;p&gt;In vsock_update_buffer_size(), the buffer size was being clamped to the
maximum first, and then to the minimum. If a user sets a minimum buffer
size larger than the maximum, the minimum check overrides the maximum
check, inverting the constraint.&lt;/p&gt;
&lt;p&gt;This breaks the intended socket memory boundaries by allowing the
vsk-&amp;gt;buffer_size to grow beyond the configured vsk-&amp;gt;buffer_max_size.&lt;/p&gt;
&lt;p&gt;Fix this by checking the minimum first, and then the maximum. This
ensures the buffer size never exceeds the buffer_max_size.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46234</guid>
    </item>
  </channel>
</rss>
