From: Fuad Tabba <fuad.tabba@linux.dev>
To: Marc Zyngier <maz@kernel.org>, Thomas Gleixner <tglx@kernel.org>
Cc: Radu Rendec <radu@rendec.net>, James Morse <james.morse@arm.com>,
Will Deacon <will@kernel.org>, Fuad Tabba <tabba@google.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] irqchip/gic-v3: Memory-safety fixes on the probe paths
Date: Thu, 24 Sep 2026 17:15:11 +0100 [thread overview]
Message-ID: <20260924161514.1112730-1-fuad.tabba@linux.dev> (raw)
Hi folks,
Three probe-time bugs in the GICv3 drivers. The kernel keeps running
after each of them, so the memory involved is live rather than on the
way to a reset.
The first two free memory an enabled ITS still points at. Boot carries
on because its_init() discards a failed probe and gic_init_bases()
discards what its_init() returns. The third is a write past the end of
redist_regs[] for an enabled GICC with a zero GICR base.
fa2dabe57220e's commit message says such tables exist, and I haven't
seen one.
Based on Linux 7.3-rc4 (93f51579e7df2).
Cheers,
/fuad
Fuad Tabba (3):
irqchip/gic-v3-its: Don't free a vPE table shared with another ITS
irqchip/gic-v3-its: Don't free the tables of an enabled ITS
irqchip/gic-v3: Don't register a redistributor that was never counted
drivers/irqchip/irq-gic-v3-its.c | 16 +++++++++++-----
drivers/irqchip/irq-gic-v3.c | 6 ++++++
2 files changed, 17 insertions(+), 5 deletions(-)
base-commit: 93f51579e7df248780214094418f205253383cc5
--
2.39.5
next reply other threads:[~2026-09-24 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:15 Fuad Tabba [this message]
2026-09-24 16:15 ` [PATCH 1/3] irqchip/gic-v3-its: Don't free a vPE table shared with another ITS Fuad Tabba
2026-09-24 16:15 ` [PATCH 2/3] irqchip/gic-v3-its: Don't free the tables of an enabled ITS Fuad Tabba
2026-09-24 16:15 ` [PATCH 3/3] irqchip/gic-v3: Don't register a redistributor that was never counted Fuad Tabba
2026-09-24 17:29 ` Marc Zyngier
2026-09-24 17:48 ` Fuad Tabba
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=20260924161514.1112730-1-fuad.tabba@linux.dev \
--to=fuad.tabba@linux.dev \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=radu@rendec.net \
--cc=tabba@google.com \
--cc=tglx@kernel.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®