[syzbot] [kernel?] kernel panic: corrupted stack end in do_idle (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 23b0f90ba871 Merge tag 'sysctl-7.00-rc1' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11e55c02580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3abe9be3d64fa6e9
dashboard link: https://syzkaller.appspot.com/bug?extid=33a3266aca8efa808d78
compiler: arm-linux-gnueabi-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: arm

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/98a89b9f34e4/non_bootable_disk-23b0f90b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9149f0c5cc36/vmlinux-23b0f90b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25a2406407e3/zImage-23b0f90b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+33a326...@syzkaller.appspotmail.com

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G L syzkaller #0 PREEMPT
Tainted: [L]=SOFTLOCKUP
Hardware name: ARM-Versatile Express
Call trace:
[<80201a14>] (dump_backtrace) from [<80201b08>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:257)
r7:8281f940 r6:00000000 r5:822a7824 r4:00000001
[<80201af0>] (show_stack) from [<8021e45c>] (__dump_stack lib/dump_stack.c:94 [inline])
[<80201af0>] (show_stack) from [<8021e45c>] (dump_stack_lvl+0x5c/0x70 lib/dump_stack.c:120)
[<8021e400>] (dump_stack_lvl) from [<8021e488>] (dump_stack+0x18/0x1c lib/dump_stack.c:129)
r7:8281f940 r6:00000000 r5:8281b680 r4:82a80d14
[<8021e470>] (dump_stack) from [<802025f4>] (vpanic+0x114/0x320 kernel/panic.c:650)
[<802024e0>] (vpanic) from [<80202834>] (trace_suspend_resume+0x0/0x104 kernel/panic.c:787)
r7:826cc400
[<80202800>] (panic) from [<81ae58c4>] (schedule_debug kernel/sched/core.c:5855 [inline])
[<80202800>] (panic) from [<81ae58c4>] (__schedule+0x13d8/0x13e0 kernel/sched/core.c:6783)
r3:57ac6e9d r2:802a33b4 r1:822a7824 r0:82298d88
[<81ae44ec>] (__schedule) from [<81ae5afc>] (schedule_idle+0x24/0x68 kernel/sched/core.c:7030)
r10:8281b0b4 r9:00000000 r8:00000000 r7:8280c590 r6:8281b680 r5:8280c550
r4:8281b680
[<81ae5ad8>] (schedule_idle) from [<802b2ee8>] (do_idle+0x17c/0x2f0 kernel/sched/idle.c:360)
r5:8280c550 r4:00000000
[<802b2d6c>] (do_idle) from [<802b336c>] (cpu_startup_entry+0x30/0x34 kernel/sched/idle.c:430)
r10:8281b0b4 r9:823d05c8 r8:00000000 r7:dddf03ec r6:8280c500 r5:82822440
r4:000000ed
[<802b333c>] (cpu_startup_entry) from [<81ae2798>] (rest_init+0xdc/0xe0 init/main.c:760)
[<81ae26bc>] (rest_init) from [<8260144c>] (start_kernel+0x824/0x840 init/main.c:1210)
[<82600c28>] (start_kernel) from [<00000000>] (0x0)
Rebooting in 86400 seconds..


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup