From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72153: irqchip/crossbar: Use correct index in crossbar_domain_free()
Date: Sat, 15 Aug 2026 15:03:52 +0900 [thread overview]
Message-ID: <2026081534-CVE-2026-72153-1828@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
irqchip/crossbar: Use correct index in crossbar_domain_free()
crossbar_domain_free() resets the domain data and then uses the nulled
out irq_data->hwirq member as index to reset the irq_map[] entry and to
write the relevant crossbar register with a safe entry. That means it
never frees the correct index and keeps the crossbar register connection
to the source interrupt active.
If it would not reset the domain data, then this would be even worse as
irq_data->hwirq holds the source interrupt number, but both the map and
register index need the corresponding GIC SPI number and not the source
interrupt number. This might even result in an out of bounds access as
the source interrupt number can be higher than the maximal index space.
Fix this by using the GIC SPI index from the parent domain's irq_data.
The Linux kernel CVE team has assigned CVE-2026-72153 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 5.10.261 with commit 13bdb5140405ff283f9052e65ee1d5c2303765c7
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 5.15.212 with commit 1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 6.1.178 with commit ccc3664679763d2d6f067c28729bdff627bb72d0
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 6.6.145 with commit 424130169dc03b84ea604685409726d61bcec859
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 6.12.97 with commit cca649a23a5fc8aae536fc27a0546c67690a4078
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 6.18.40 with commit 36ca587f55a2c04468a89fd16174bb2f78dc04ec
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 7.1.5 with commit e5be5d452d5f1efbb3342da2b00029be6c99034e
Issue introduced in 4.1 with commit 783d31863fb826f1a3754a2d5959a022a1b12d54 and fixed in 7.2-rc1 with commit 043db005a8d6932dc7d217c86307e9af0bc10ddc
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-72153
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/irqchip/irq-crossbar.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/13bdb5140405ff283f9052e65ee1d5c2303765c7
https://git.kernel.org/stable/c/1c48dc6a0c1ef47a9fa24611e60bc2f4ee4dd0df
https://git.kernel.org/stable/c/ccc3664679763d2d6f067c28729bdff627bb72d0
https://git.kernel.org/stable/c/424130169dc03b84ea604685409726d61bcec859
https://git.kernel.org/stable/c/cca649a23a5fc8aae536fc27a0546c67690a4078
https://git.kernel.org/stable/c/36ca587f55a2c04468a89fd16174bb2f78dc04ec
https://git.kernel.org/stable/c/e5be5d452d5f1efbb3342da2b00029be6c99034e
https://git.kernel.org/stable/c/043db005a8d6932dc7d217c86307e9af0bc10ddc
reply other threads:[~2026-08-15 6:13 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=2026081534-CVE-2026-72153-1828@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.