<?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 14:29:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89455 — PCI: plda: Fix use-after-free of event IRQs during teardown</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89455</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;PCI: plda: Fix use-after-free of event IRQs during teardown&lt;/p&gt;
&lt;p&gt;plda_pcie_irq_domain_deinit() removes pcie-&amp;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.&lt;/p&gt;
&lt;p&gt;This means irq_domain_remove() can free the domain&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Also dispose of the event, INTx, and MSI IRQ mappings with
irq_dispose_mapping() before their owning domains are removed.&lt;/p&gt;
&lt;p&gt;Finally, guard the calls to irq_set_chained_handler_and_data() for
pcie-&amp;gt;irq, pcie-&amp;gt;msi_irq, and pcie-&amp;gt;intx_irq so they only run when
those fields hold a valid (&amp;gt;0) IRQ number.&lt;/p&gt;
&lt;p&gt;This is a pre-existing issue, flagged by automated review during work
on an earlier, unrelated patch to this driver.&lt;/p&gt;
&lt;p&gt;Build-tested and boot-tested on StarFive VisionFive v1.2A board&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;PCI: plda: Fix use-after-free of event IRQs during teardown&lt;/p&gt;
&lt;p&gt;plda_pcie_irq_domain_deinit() removes pcie-&amp;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.&lt;/p&gt;
&lt;p&gt;This means irq_domain_remove() can free the domain&amp;#39;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Also dispose of the event, INTx, and MSI IRQ mappings with
irq_dispose_mapping() before their owning domains are removed.&lt;/p&gt;
&lt;p&gt;Finally, guard the calls to irq_set_chained_handler_and_data() for
pcie-&amp;gt;irq, pcie-&amp;gt;msi_irq, and pcie-&amp;gt;intx_irq so they only run when
those fields hold a valid (&amp;gt;0) IRQ number.&lt;/p&gt;
&lt;p&gt;This is a pre-existing issue, flagged by automated review during work
on an earlier, unrelated patch to this driver.&lt;/p&gt;
&lt;p&gt;Build-tested and boot-tested on StarFive VisionFive v1.2A board&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89455</guid>
    </item>
  </channel>
</rss>
