<?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>Fri, 02 Oct 2026 15:26:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72483 — usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72483</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: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()&lt;/p&gt;
&lt;p&gt;The `max3421_hub_control()` function handles USB hub class requests
to the virtual root hub. In the `default` branches of both the
`ClearPortFeature` and `SetPortFeature` switch statements, it modifies
`max3421_hcd-&amp;gt;port_status` by left shifting 1 by the request&amp;#39;s `value`
parameter. However, it does not validate whether this shift will exceed
the width of `port_status`.&lt;/p&gt;
&lt;p&gt;So if a malicious userspace task with access to the root hub via
/dev/bus/usb/.../001 issues a USBDEVFS_CONTROL ioctl with `wValue`
greater than or equal to 32, the left shift operation invokes
shift-out-of-bounds undefined behavior. This results in arbitrary
bit corruption of `port_status`, including the normally-immutable
change bits, which can bypass internal state checks and confuse the
hub status.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting requests whose `value` exceeds the shift width
before performing the shift.&lt;/p&gt;
&lt;p&gt;This issue was found using a KLEE-based symbolic execution tool for
kernel drivers that I&amp;#39;m currently developing.&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: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()&lt;/p&gt;
&lt;p&gt;The `max3421_hub_control()` function handles USB hub class requests
to the virtual root hub. In the `default` branches of both the
`ClearPortFeature` and `SetPortFeature` switch statements, it modifies
`max3421_hcd-&amp;gt;port_status` by left shifting 1 by the request&amp;#39;s `value`
parameter. However, it does not validate whether this shift will exceed
the width of `port_status`.&lt;/p&gt;
&lt;p&gt;So if a malicious userspace task with access to the root hub via
/dev/bus/usb/.../001 issues a USBDEVFS_CONTROL ioctl with `wValue`
greater than or equal to 32, the left shift operation invokes
shift-out-of-bounds undefined behavior. This results in arbitrary
bit corruption of `port_status`, including the normally-immutable
change bits, which can bypass internal state checks and confuse the
hub status.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting requests whose `value` exceeds the shift width
before performing the shift.&lt;/p&gt;
&lt;p&gt;This issue was found using a KLEE-based symbolic execution tool for
kernel drivers that I&amp;#39;m currently developing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72483</guid>
    </item>
  </channel>
</rss>
