<?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-09-30T08:34:38.525566+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-89633</id>
    <title>CVE-2026-89633 — smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()</title>
    <updated>2026-09-30T08:34:38.540734+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 OOB read/write from unvalidated DataOffset in coalesce_t2()</p>
<p>coalesce_t2() computes data pointers directly from server-supplied
DataOffset fields with no validation against buffer bounds:</p>
<p>data_area_of_tgt = (char *)&amp;pSMBt-&gt;hdr.Protocol +
                     get_unaligned_le16(&amp;pSMBt-&gt;t2_rsp.DataOffset);
  data_area_of_src = (char *)&amp;pSMBs-&gt;hdr.Protocol +
                     get_unaligned_le16(&amp;pSMBs-&gt;t2_rsp.DataOffset);
  data_area_of_tgt += total_in_tgt;
  ...
  memcpy(data_area_of_tgt, data_area_of_src, total_in_src);</p>
<p>A small DataOffset can push a pointer below the actual byte area,
overwriting header fields; a large one can push it past the buffer
end, causing out-of-bounds heap reads (source) or writes (target).
The BCC overflow guard does not prevent this: BCC reflects how much
data is present, while DataOffset controls where in the buffer it
starts.</p>
<p>The "validate target area" comment present since the function was
first written in 2005 was a placeholder that was never implemented.</p>
<p>Add lower- and upper-bound checks for both data pointers before the
memcpy, and before any target header fields are modified.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89633"/>
  </entry>
</feed>
