GHSA-8QQP-MRFH-PVX7
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In 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": [],
"aliases": [
"CVE-2026-89455"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:26Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: plda: Fix use-after-free of event IRQs during teardown\n\nplda_pcie_irq_domain_deinit() removes pcie-\u003eevent_domain via\nirq_domain_remove(), but the per-event IRQs mapped from that domain\nare requested with devm_request_irq() in plda_init_interrupts(). The\nactual free_irq() for a devm-managed IRQ is deferred by devres until\nafter the calling probe()/remove() function returns.\n\nThis means irq_domain_remove() can free the domain\u0027s internal data\nbefore the deferred free_irq() for IRQs still mapped into it has run.\nWhen devres later processes that deferred cleanup, it can end up\ndereferencing the already-freed domain.\n\nFree each event IRQ explicitly with devm_free_irq() before removing\nthe domain. This triggers the free immediately and removes the IRQ\nfrom the devres tracking list, so devres will not attempt to free it\na second time later.\n\nAlso dispose of the event, INTx, and MSI IRQ mappings with\nirq_dispose_mapping() before their owning domains are removed.\n\nFinally, guard the calls to irq_set_chained_handler_and_data() for\npcie-\u003eirq, pcie-\u003emsi_irq, and pcie-\u003eintx_irq so they only run when\nthose fields hold a valid (\u003e0) IRQ number.\n\nThis is a pre-existing issue, flagged by automated review during work\non an earlier, unrelated patch to this driver.\n\nBuild-tested and boot-tested on StarFive VisionFive v1.2A board",
"id": "GHSA-8qqp-mrfh-pvx7",
"modified": "2026-09-11T21:31:26Z",
"published": "2026-09-11T21:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89455"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/01c2f0c66bd1f892db9c6e82976da6b463cc4427"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1d0159e139261996a3ca21798d9114aab2124d3c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/26b73bae01d6eb81a4a38f36101812f20b2639de"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e3589ca5f2e6477774753a2202c21509428d4701"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.