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