<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:38:11.237706+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-92521</id>
    <title>CVE-2026-92521 — ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root</title>
    <updated>2026-09-30T23:38:11.240491+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>ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root</p>
<p>acpi_pci_root_add() assigns the freshly allocated root to
device-&gt;driver_data before dmar_device_add() and pci_acpi_scan_root().
Both failure paths reach the end: label where root is kfree()'d, but
only the pci_acpi_scan_root() path clears driver_data first.</p>
<p>When dmar_device_add() fails during a hot-add, root is freed while
device-&gt;driver_data still points at it.  The ACPI core does not clear
driver_data on attach failure, so a later acpi_pci_find_root() call may
dereference this dangling pointer.</p>
<p>acpi_pci_root_remove() has the same problem: it frees root without
clearing device-&gt;driver_data, leaving a dangling pointer behind after
the root bridge is removed.</p>
<p>Move the NULL assignment to the shared end: label so every error path in
acpi_pci_root_add() clears driver_data before freeing root, and clear it
in acpi_pci_root_remove() as well, so the object is never left reachable
through driver_data after being freed.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-92521"/>
  </entry>
</feed>
