From: Aaron Tomlin <atomlin@atomlin.com>
To: tglx@kernel.org
Cc: neelx@suse.com, sean@ashe.io, steve@abita.co, mproche@gmail.com,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH] genirq: Enforce monotonic increase contract in irq_get_next_irq()
Date: Wed, 3 Jun 2026 22:01:49 -0400 [thread overview]
Message-ID: <20260604020149.1148697-1-atomlin@atomlin.com> (raw)
When an IRQ descriptor is corrupted in memory (e.g., via an out-of-bounds
write by a rogue driver), the descriptor's internal IRQ number may be
zeroed out.
During iteration via for_each_active_irq(), irq_get_next_irq() relies on
irq_desc_get_irq(desc) to retrieve the next IRQ number. If a descriptor is
corrupted, this can result in returning an IRQ number (e.g., 0) that is
strictly less than the requested offset. This breaks the fundamental
forward-progress guarantee of the iterator.
This contract violation causes catastrophic unsigned integer underflows in
callers. For instance, show_all_irqs() in fs/proc/stat.c calculates
padding using (i - next). A corrupted descriptor returning 0 forces a
massive unsigned underflow, trapping the CPU in an extensive loop inside
show_irq_gap() and triggering a soft lockup watchdog.
While the underlying issue is a memory corruption bug, core iterators
should be resilient against returning values that violate their own
mathematical boundaries and induce lockups in other subsystems.
Introduce a lightweight boundary check in irq_get_next_irq() to verify
the returned IRQ is greater than or equal to the offset. If corruption
is detected, raise a WARN_ONCE() to pinpoint the invalid state and
return nr_irqs to safely abort the iteration.
Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
---
kernel/irq/irqdesc.c | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c
index 7173b8b634f2..47a9dedb36b3 100644
--- a/kernel/irq/irqdesc.c
+++ b/kernel/irq/irqdesc.c
@@ -927,7 +927,22 @@ EXPORT_SYMBOL_GPL(__irq_alloc_descs);
*/
unsigned int irq_get_next_irq(unsigned int offset)
{
- return irq_find_at_or_after(offset);
+ unsigned int irq;
+ const unsigned int nr_irqs = irq_get_nr_irqs();
+
+ irq = irq_find_at_or_after(offset);
+
+ /*
+ * Defend against corrupted IRQ descriptors violating the monotonic
+ * iterator contract. Returning a value lower than the offset will
+ * cause catastrophic unsigned underflows in callers.
+ */
+ if (WARN_ONCE(irq < offset && irq < nr_irqs,
+ "genirq: Corrupted IRQ descriptor detected: irq %u < offset %u\n",
+ irq, offset))
+ return nr_irqs;
+
+ return irq;
}
struct irq_desc *__irq_get_desc_lock(unsigned int irq, unsigned long *flags, bool bus,
--
2.51.0
next reply other threads:[~2026-06-04 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 2:01 Aaron Tomlin [this message]
2026-06-04 9:21 ` Thomas Gleixner
2026-06-04 13:23 ` Aaron Tomlin
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=20260604020149.1148697-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mproche@gmail.com \
--cc=neelx@suse.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
--cc=tglx@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
Powered by JetHome