<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T04:16:10.668234+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-64381</id>
    <title>CVE-2026-64381 — smb: client: Fix next buffer leak in receive_encrypted_standard()</title>
    <updated>2026-10-04T04:16:11.507023+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>smb: client: Fix next buffer leak in receive_encrypted_standard()</p>
<p>receive_encrypted_standard() allocates next_buffer before checking
whether the number of compound PDUs already reached MAX_COMPOUND. If
the limit check fails, the function returns immediately and the newly
allocated next_buffer is not assigned to server-&gt;smallbuf/server-&gt;bigbuf,
making it leaked.</p>
<p>Move the MAX_COMPOUND check before allocating next_buffer.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64381"/>
  </entry>
</feed>
