CVE-2026-89455

published 11 Sep 2026 · updated 15 Nov 2026

PCI: plda: Fix use-after-free of event IRQs during teardown

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e3589ca5f2e6477774753a2202c21509428d4701, Kernel 01c2f0c66bd1f892db9c6e82976da6b463cc4427, Kernel 1d0159e139261996a3ca21798d9114aab2124d3c and 4 more.

In the Linux kernel, the following vulnerability has been resolved: PCI: plda: Fix use-after-free of event IRQs during teardown plda_pcie_irq_domain_deinit() removes pcie->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. 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. 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. Also dispose of the event, INTx, and MSI IRQ mappings with irq_dispose_mapping() before their owning domains are removed. Finally, guard the calls to irq_set_chained_handler_and_data() for pcie->irq, pcie->msi_irq, and pcie->intx_irq so they only run when those fields hold a valid (>0) IRQ number. This is a pre-existing issue, flagged by automated review during work on an earlier, unrelated patch to this driver. Build-tested and boot-tested on StarFive VisionFive v1.2A board

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=76c9113968079140cb2f885631db422170f32105 <e3589ca5f2e6477774753a2202c21509428d4701, >=76c9113968079140cb2f885631db422170f32105 <01c2f0c66bd1f892db9c6e82976da6b463cc4427, >=76c9113968079140cb2f885631db422170f32105 <1d0159e139261996a3ca21798d9114aab2124d3c, >=76c9113968079140cb2f885631db422170f32105 <26b73bae01d6eb81a4a38f36101812f20b2639de, =6.11e3589ca5f2e6477774753a2202c21509428d4701, 01c2f0c66bd1f892db9c6e82976da6b463cc4427, 1d0159e139261996a3ca21798d9114aab2124d3c, 26b73bae01d6eb81a4a38f36101812f20b2639de
linux-kernel: Kernel>=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.11.0 <6.12.1096.18.50, 7.2.4, 6.12.109

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89455 severity on Zeptric[![CVE-2026-89455](https://zeptric.io/badge/cve/CVE-2026-89455.svg)](https://zeptric.io/cve/CVE-2026-89455)