<?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>Sun, 04 Oct 2026 15:26:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80827 — USB: serial: option: fix slab OOB read in interrupt URB callback</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80827</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;USB: serial: option: fix slab OOB read in interrupt URB callback&lt;/p&gt;
&lt;p&gt;The interrupt URB buffer is allocated in setup_port_interrupt_in() based
on the endpoint&amp;#39;s wMaxPacketSize:&lt;/p&gt;
&lt;p&gt;buffer_size = usb_endpoint_maxp(epd);
    port-&amp;gt;interrupt_in_buffer = kmalloc(buffer_size, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;When a USB device declares wMaxPacketSize = 8 on its interrupt IN
endpoint, the buffer is allocated from kmalloc-8 cache (exactly
8 bytes).&lt;/p&gt;
&lt;p&gt;If the device sends a short packet (actual_length &amp;lt; wMaxPacketSize),
the URB completes with status == 0 and the callback proceeds to read:&lt;/p&gt;
&lt;p&gt;data[sizeof(struct usb_ctrlrequest)]&lt;/p&gt;
&lt;p&gt;which evaluates to data[8], accessing 1 byte beyond the allocated 8-byte
buffer. This results in a slab out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing bounds check: first verify that the
actual length is large enough to contain the struct usb_ctrlrequest
header before accessing req_pkt-&amp;gt;bRequestType and req_pkt-&amp;gt;bRequest,
and then verify that there is an additional byte for the modem signal
state before reading data[sizeof(struct usb_ctrlrequest)] inside the
conditional.  Use sizeof(*req_pkt) instead of sizeof(struct
usb_ctrlrequest) for consistency.&lt;/p&gt;
&lt;p&gt;[ johan: use dev_err(); split signals declaration and initialisation ]&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;USB: serial: option: fix slab OOB read in interrupt URB callback&lt;/p&gt;
&lt;p&gt;The interrupt URB buffer is allocated in setup_port_interrupt_in() based
on the endpoint&amp;#39;s wMaxPacketSize:&lt;/p&gt;
&lt;p&gt;buffer_size = usb_endpoint_maxp(epd);
    port-&amp;gt;interrupt_in_buffer = kmalloc(buffer_size, GFP_KERNEL);&lt;/p&gt;
&lt;p&gt;When a USB device declares wMaxPacketSize = 8 on its interrupt IN
endpoint, the buffer is allocated from kmalloc-8 cache (exactly
8 bytes).&lt;/p&gt;
&lt;p&gt;If the device sends a short packet (actual_length &amp;lt; wMaxPacketSize),
the URB completes with status == 0 and the callback proceeds to read:&lt;/p&gt;
&lt;p&gt;data[sizeof(struct usb_ctrlrequest)]&lt;/p&gt;
&lt;p&gt;which evaluates to data[8], accessing 1 byte beyond the allocated 8-byte
buffer. This results in a slab out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing bounds check: first verify that the
actual length is large enough to contain the struct usb_ctrlrequest
header before accessing req_pkt-&amp;gt;bRequestType and req_pkt-&amp;gt;bRequest,
and then verify that there is an additional byte for the modem signal
state before reading data[sizeof(struct usb_ctrlrequest)] inside the
conditional.  Use sizeof(*req_pkt) instead of sizeof(struct
usb_ctrlrequest) for consistency.&lt;/p&gt;
&lt;p&gt;[ johan: use dev_err(); split signals declaration and initialisation ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80827</guid>
    </item>
  </channel>
</rss>
