<?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-29T03:05:49.849630+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-2026-89455</id>
    <title>CVE-2026-89455 — PCI: plda: Fix use-after-free of event IRQs during teardown</title>
    <updated>2026-09-29T03:05:51.170906+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>PCI: plda: Fix use-after-free of event IRQs during teardown</p>
<p>plda_pcie_irq_domain_deinit() removes pcie-&gt;event_domain via
irq_domain_remove(), but the per-event IRQs mapped from that domain
are requested with devm_request_irq() in plda_init_interrupts(). The
actual free_irq() for a devm-managed IRQ is deferred by devres until
after the calling probe()/remove() function returns.</p>
<p>This means irq_domain_remove() can free the domain's internal data
before the deferred free_irq() for IRQs still mapped into it has run.
When devres later processes that deferred cleanup, it can end up
dereferencing the already-freed domain.</p>
<p>Free each event IRQ explicitly with devm_free_irq() before removing
the domain. This triggers the free immediately and removes the IRQ
from the devres tracking list, so devres will not attempt to free it
a second time later.</p>
<p>Also dispose of the event, INTx, and MSI IRQ mappings with
irq_dispose_mapping() before their owning domains are removed.</p>
<p>Finally, guard the calls to irq_set_chained_handler_and_data() for
pcie-&gt;irq, pcie-&gt;msi_irq, and pcie-&gt;intx_irq so they only run when
those fields hold a valid (&gt;0) IRQ number.</p>
<p>This is a pre-existing issue, flagged by automated review during work
on an earlier, unrelated patch to this driver.</p>
<p>Build-tested and boot-tested on StarFive VisionFive v1.2A board</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89455"/>
  </entry>
</feed>
