CVE-2026-89455

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 76c9113968079140cb2f885631db422170f32105, 6.11, <01c2f0c66bd1f892db9c6e82976da6b463cc4427, <=*, <=6.12.*, <26b73bae01d6eb81a4a38f36101812f20b2639de, <=6.18.*, 6.18.50, <1d0159e139261996a3ca21798d9114aab2124d3c, 0, <=7.2.*, 6.12.109, 7.2.4, <e3589ca5f2e6477774753a2202c21509428d4701, <6.11, 7.3

Description

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

Gravité et risque d'exploitation

CVE-2026-89455 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 9.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 76c9113968079140cb2f885631db422170f32105, 6.11, <01c2f0c66bd1f892db9c6e82976da6b463cc4427, <=*, <=6.12.*, <26b73bae01d6eb81a4a38f36101812f20b2639de, <=6.18.*, 6.18.50, <1d0159e139261996a3ca21798d9114aab2124d3c, 0, <=7.2.*, 6.12.109, 7.2.4, <e3589ca5f2e6477774753a2202c21509428d4701, <6.11, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références