From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89454: PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts()
Date: Fri, 11 Sep 2026 21:42:23 +0200 [thread overview]
Message-ID: <2026091159-CVE-2026-89454-8b16@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts()
plda_init_interrupts() initializes IRQ domains and creates IRQ mapping but
does not unwind them when later step fails.
If platform_get_irq() or either irq_create_mapping() fails
in plda_init_interrupts(), the domains are never deinitialized. If
irq_create_mapping() fails, port->intx_irq stays initialized.
Hence, remove the IRQ domains in the error path by calling
plda_pcie_irq_domain_deinit().
Since plda_pcie_irq_domain_deinit() now disposes of the intx_irq and
msi_irq mappings itself before removing their domains, the msi_irq
mapping failure path can go directly to err_irq_domain_deinit instead of
disposing of port->intx_irq separately first.
This issue was found by automated review of sashiko-bot
[mani: commit log]
The Linux kernel CVE team has assigned CVE-2026-89454 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 4602c370bdf6946b4e954a3db0ef5958aac2b7b4 and fixed in 6.12.109 with commit 01b05cebe1e862e31e382359848d7dca02525a4f
Issue introduced in 6.11 with commit 4602c370bdf6946b4e954a3db0ef5958aac2b7b4 and fixed in 6.18.50 with commit 4b575052ea65423693726a21826d783cf3f1745e
Issue introduced in 6.11 with commit 4602c370bdf6946b4e954a3db0ef5958aac2b7b4 and fixed in 7.2.4 with commit e54e8d2a0f9c8bf251ae4385ea4f4a68840fedad
Issue introduced in 6.11 with commit 4602c370bdf6946b4e954a3db0ef5958aac2b7b4 and fixed in 7.3-rc1 with commit 19a30bbb6477bfd7e3109b7a2943e6597ee9de37
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89454
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/pci/controller/plda/pcie-plda-host.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/01b05cebe1e862e31e382359848d7dca02525a4f
https://git.kernel.org/stable/c/4b575052ea65423693726a21826d783cf3f1745e
https://git.kernel.org/stable/c/e54e8d2a0f9c8bf251ae4385ea4f4a68840fedad
https://git.kernel.org/stable/c/19a30bbb6477bfd7e3109b7a2943e6597ee9de37
reply other threads:[~2026-09-11 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091159-CVE-2026-89454-8b16@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.