<?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-10-03T03:23:38.280996+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-2025-38134</id>
    <title>CVE-2025-38134 — usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()</title>
    <updated>2026-10-03T03:23:38.282762+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: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()</p>
<p>As demonstrated by the fix for update_port_device_state,
commit 12783c0b9e2c ("usb: core: Prevent null pointer dereference in update_port_device_state"),
usb_hub_to_struct_hub() can return NULL in certain scenarios,
such as during hub driver unbind or teardown race conditions,
even if the underlying usb_device structure exists.</p>
<p>Plus, all other places that call usb_hub_to_struct_hub() in the same file
do check for NULL return values.</p>
<p>If usb_hub_to_struct_hub() returns NULL, the subsequent access to
hub-&gt;ports[udev-&gt;portnum - 1] will cause a null pointer dereference.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38134"/>
  </entry>
</feed>
