<?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>Wed, 30 Sep 2026 03:43:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64257 — smb: client: reject overlapping data areas in SMB2 responses</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64257</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;smb: client: reject overlapping data areas in SMB2 responses&lt;/p&gt;
&lt;p&gt;Commit 53b7c271f06b (&amp;#34;smb: client: restrict implied bcc[0] exemption to
responses without data area&amp;#34;) restricted the implied bcc[0] length
exception to responses without a data area. However, the overlap
handling in __smb2_calc_size() clears data_length, which can make an
invalid response appear to have no data area and so qualify for the
exception.&lt;/p&gt;
&lt;p&gt;Track data area overlap separately and reject such responses before
applying the length compatibility exceptions.&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;smb: client: reject overlapping data areas in SMB2 responses&lt;/p&gt;
&lt;p&gt;Commit 53b7c271f06b (&amp;#34;smb: client: restrict implied bcc[0] exemption to
responses without data area&amp;#34;) restricted the implied bcc[0] length
exception to responses without a data area. However, the overlap
handling in __smb2_calc_size() clears data_length, which can make an
invalid response appear to have no data area and so qualify for the
exception.&lt;/p&gt;
&lt;p&gt;Track data area overlap separately and reject such responses before
applying the length compatibility exceptions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64257</guid>
    </item>
  </channel>
</rss>
