<?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 07:05:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-45027 — usb: xhci: Check for xhci-&gt;interrupters being allocated in xhci_mem_clearup()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-45027</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: xhci: Check for xhci-&amp;gt;interrupters being allocated in xhci_mem_clearup()&lt;/p&gt;
&lt;p&gt;If xhci_mem_init() fails, it calls into xhci_mem_cleanup() to mop
up the damage. If it fails early enough, before xhci-&amp;gt;interrupters
is allocated but after xhci-&amp;gt;max_interrupters has been set, which
happens in most (all?) cases, things get uglier, as xhci_mem_cleanup()
unconditionally derefences xhci-&amp;gt;interrupters. With prejudice.&lt;/p&gt;
&lt;p&gt;Gate the interrupt freeing loop with a check on xhci-&amp;gt;interrupters
being non-NULL.&lt;/p&gt;
&lt;p&gt;Found while debugging a DMA allocation issue that led the XHCI driver
on this exact path.&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: xhci: Check for xhci-&amp;gt;interrupters being allocated in xhci_mem_clearup()&lt;/p&gt;
&lt;p&gt;If xhci_mem_init() fails, it calls into xhci_mem_cleanup() to mop
up the damage. If it fails early enough, before xhci-&amp;gt;interrupters
is allocated but after xhci-&amp;gt;max_interrupters has been set, which
happens in most (all?) cases, things get uglier, as xhci_mem_cleanup()
unconditionally derefences xhci-&amp;gt;interrupters. With prejudice.&lt;/p&gt;
&lt;p&gt;Gate the interrupt freeing loop with a check on xhci-&amp;gt;interrupters
being non-NULL.&lt;/p&gt;
&lt;p&gt;Found while debugging a DMA allocation issue that led the XHCI driver
on this exact path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-45027</guid>
    </item>
  </channel>
</rss>
