<?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-01T15:33:40.474885+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-64339</id>
    <title>CVE-2026-64339 — usb: misc: usbio: bound bulk IN response length to the received transfer</title>
    <updated>2026-10-01T15:33:40.478102+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>usb: misc: usbio: bound bulk IN response length to the received transfer</p>
<p>usbio_bulk_msg() copies bpkt_len = le16_to_cpu(bpkt-&gt;len) bytes out of
the bulk IN buffer (usbio-&gt;rxbuf, allocated with size usbio-&gt;rxbuf_len)
into the caller's buffer.  bpkt_len is fully controlled by the device
and is only checked against ibuf_len; ibuf_len in turn is checked
against usbio-&gt;txbuf_len, not against rxbuf_len:</p>
<p>if ((obuf_len &gt; (usbio-&gt;txbuf_len - sizeof(*bpkt))) ||
	    (ibuf_len &gt; (usbio-&gt;txbuf_len - sizeof(*bpkt))))
		return -EMSGSIZE;</p>
<p>txbuf_len and rxbuf_len are taken independently from the bulk OUT and
bulk IN endpoint wMaxPacketSize in usbio_probe().  A malicious or
malfunctioning device that advertises a large bulk OUT endpoint and a
small bulk IN endpoint (e.g. by claiming one of the quirk-free IDs such
as the Lattice NX33U, 0x2ac1:0x20cb) therefore makes ibuf_len, and
hence the device-supplied bpkt_len, exceed rxbuf_len.  memcpy() then
reads up to txbuf_len - rxbuf_len bytes past the end of the rxbuf slab
object.  The over-read bytes are handed back to the i2c layer and on to
user space through i2c-dev, disclosing adjacent slab memory; with KASAN
this is reported as a slab-out-of-bounds read.</p>
<p>The number of bytes actually received is already known: act equals the
URB actual_length and is bounded by rxbuf_len.  Reject any response
that claims more payload than was received, mirroring the existing
"act &lt; sizeof…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64339"/>
  </entry>
</feed>
