<?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>Tue, 29 Sep 2026 16:00:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64351 — net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64351</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;net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()&lt;/p&gt;
&lt;p&gt;kalmia_rx_fixup() computes usb_packet_length = skb-&amp;gt;len - (2 *
KALMIA_HEADER_LENGTH) as a u16, guarded only by a pre-loop check that
skb-&amp;gt;len is at least KALMIA_HEADER_LENGTH, which is 6. A device can
deliver a short bulk-IN frame with skb-&amp;gt;len in the 6 to 11 range, or
leave a short trailing remainder on a later loop iteration. Either case
underflows usb_packet_length to about 65530.&lt;/p&gt;
&lt;p&gt;That bypasses the usb_packet_length &amp;lt; ether_packet_length truncation path.
The device-supplied ether_packet_length, a le16 up to 65535 read from
header_start[2], then drives a memcmp() and the following skb_trim() and
skb_pull() past the end of the rx buffer. The rx buffer is hard_mtu * 10,
which is 14000 bytes. That is an out of bounds read.&lt;/p&gt;
&lt;p&gt;Require both the start and end framing headers to be present before
subtracting them, on every loop iteration.&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;net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()&lt;/p&gt;
&lt;p&gt;kalmia_rx_fixup() computes usb_packet_length = skb-&amp;gt;len - (2 *
KALMIA_HEADER_LENGTH) as a u16, guarded only by a pre-loop check that
skb-&amp;gt;len is at least KALMIA_HEADER_LENGTH, which is 6. A device can
deliver a short bulk-IN frame with skb-&amp;gt;len in the 6 to 11 range, or
leave a short trailing remainder on a later loop iteration. Either case
underflows usb_packet_length to about 65530.&lt;/p&gt;
&lt;p&gt;That bypasses the usb_packet_length &amp;lt; ether_packet_length truncation path.
The device-supplied ether_packet_length, a le16 up to 65535 read from
header_start[2], then drives a memcmp() and the following skb_trim() and
skb_pull() past the end of the rx buffer. The rx buffer is hard_mtu * 10,
which is 14000 bytes. That is an out of bounds read.&lt;/p&gt;
&lt;p&gt;Require both the start and end framing headers to be present before
subtracting them, on every loop iteration.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64351</guid>
    </item>
  </channel>
</rss>
