From: Radu Rendec <radu@rendec.net>
To: Farhad Alemi <farhad.alemi@berkeley.edu>,
Thomas Gleixner <tglx@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: falemi@asu.edu, linux-kernel@vger.kernel.org
Subject: Re: [BUG] KASAN: slab-use-after-free Read in irq_migrate_all_off_this_cpu
Date: Sat, 29 Aug 2026 16:34:47 -0400 [thread overview]
Message-ID: <31cd7357e666ecc74b7a995641b3de3c0aa1bd0b.camel@rendec.net> (raw)
In-Reply-To: <CA+0ovCh1hKPQ3DSXBdaf3MHGZKv3-mbSNiWrAETr62mDd1weKg@mail.gmail.com>
Hello Farhad,
On Thu, 2026-08-27 at 22:41 -0700, Farhad Alemi wrote:
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/164-kasan-slab-use-after-free-read-in-irq-migrate-all-off-this-cpu/
>
> BUG: KASAN: slab-use-after-free in irq_can_move_pcntxt
> kernel/irq/internals.h:305 [inline]
> BUG: KASAN: slab-use-after-free in migrate_one_irq
> kernel/irq/cpuhotplug.c:57 [inline]
> BUG: KASAN: slab-use-after-free in
> irq_migrate_all_off_this_cpu+0xdf/0xc80 kernel/irq/cpuhotplug.c:181
> Call Trace:
> irq_can_move_pcntxt kernel/irq/internals.h:305 [inline]
> migrate_one_irq kernel/irq/cpuhotplug.c:57 [inline]
> irq_migrate_all_off_this_cpu+0xdf/0xc80 kernel/irq/cpuhotplug.c:181
> fixup_irqs+0x18/0x1e0 arch/x86/kernel/irq.c:527
> cpu_disable_common+0xb27/0xd90 arch/x86/kernel/smpboot.c:1354
> native_cpu_disable+0x2f/0x40 arch/x86/kernel/smpboot.c:1366
> take_cpu_down+0xca/0x330 kernel/cpu.c:1282
> multi_cpu_stop+0x227/0x420 kernel/stop_machine.c:238
> cpu_stopper_thread+0x259/0x3e0 kernel/stop_machine.c:512
>
> BUG: KASAN: slab-out-of-bounds in
> irq_migrate_all_off_this_cpu+0xdf/0xc80 kernel/irq/cpuhotplug.c:181
Thanks for reporting this. For everyone interested, please note that it
had been also reported by syzbot a few days before:
https://lore.kernel.org/all/6a8c23a0.dbb3a75c.7844.0001.GAE@google.com/
Currently there is no follow up to the syzbot report.
> Our reproducer.c is available upon request.
If you could please send me the reproducer, I'd be happy to take a
look.
> Happy to test a patch if that would help.
Thanks. If I figure it out and send a patch, I'll be sure to copy you.
--
Regards,
Radu
next prev parent reply other threads:[~2026-08-29 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:41 Farhad Alemi
2026-08-29 20:34 ` Radu Rendec [this message]
2026-08-30 6:24 ` Thomas Gleixner
2026-08-30 14:16 ` Mark Brown
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=31cd7357e666ecc74b7a995641b3de3c0aa1bd0b.camel@rendec.net \
--to=radu@rendec.net \
--cc=broonie@kernel.org \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®