From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64462: PCI: altera: Fix resource leaks on probe failure
Date: Sat, 25 Jul 2026 10:51:19 +0200 [thread overview]
Message-ID: <2026072543-CVE-2026-64462-85ea@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
PCI: altera: Fix resource leaks on probe failure
The chained IRQ handler is set during probe, but is only removed during the
driver remove(). If pci_host_probe() fails, the handler and INTx IRQ
domain remain set even though the devm-managed host bridge storage
containing struct altera_pcie will be released, leaving the handler with
a stale data pointer.
Interrupts are also enabled before pci_host_probe() is called. If probe
fails after that point, the controller interrupt source should be disabled
before the chained handler and INTx domain are removed.
So set the chained handler only after the INTx domain has been created.
Disable controller interrupts during IRQ teardown, and tear the IRQ setup
down if pci_host_probe() fails.
[mani: commit log]
The Linux kernel CVE team has assigned CVE-2026-64462 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 5.10.261 with commit af7cf5d56d7d57c4fbfdb7b5b693790f331b07b7
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 5.15.212 with commit 9cf0cc481e1645ec65e61486ae41c486c59781cb
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 6.1.178 with commit 99fc088d6cc6890ae35fa2f29c50ebe027844c20
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 6.6.145 with commit a25bfa2a6665a1d77324d4a609e7513b87680227
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 6.12.97 with commit 0db9aa9ec51be0a0ffdcdfd9af2b7bf3aeb7911a
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 6.18.39 with commit 09c43b7b7d29c6fadb27f32cdf7f3bb6598befa9
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 7.1.4 with commit 6864c789b570e57f932847fa83f6b56917182d73
Issue introduced in 5.9 with commit c63aed7334c21de8d626ff028ccad98cf5847a0e and fixed in 7.2-rc1 with commit 7a94138caeb27f3c49c1dbd93bf422098925bb28
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-64462
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/pcie-altera.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/af7cf5d56d7d57c4fbfdb7b5b693790f331b07b7
https://git.kernel.org/stable/c/9cf0cc481e1645ec65e61486ae41c486c59781cb
https://git.kernel.org/stable/c/99fc088d6cc6890ae35fa2f29c50ebe027844c20
https://git.kernel.org/stable/c/a25bfa2a6665a1d77324d4a609e7513b87680227
https://git.kernel.org/stable/c/0db9aa9ec51be0a0ffdcdfd9af2b7bf3aeb7911a
https://git.kernel.org/stable/c/09c43b7b7d29c6fadb27f32cdf7f3bb6598befa9
https://git.kernel.org/stable/c/6864c789b570e57f932847fa83f6b56917182d73
https://git.kernel.org/stable/c/7a94138caeb27f3c49c1dbd93bf422098925bb28
reply other threads:[~2026-07-25 9:00 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=2026072543-CVE-2026-64462-85ea@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.