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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fab1beda7597 Merge tag 'devicetree-fixes-for-6.17-1' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=173397bc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a0e1d867e9c0695
dashboard link: https://syzkaller.appspot.com/bug?extid=0b28503bc99a1a0f684d
compiler: arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm
CC: [linux-...@vger.kernel.org]

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-fab1beda.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/67fcee9f3a49/vmlinux-fab1beda.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92155cd60148/zImage-fab1beda.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT
Hardware name: ARM-Versatile Express
Call trace:
[<80201a24>] (dump_backtrace) from [<80201b20>] (show_stack+0x18/0x1c arch/arm/kernel/traps.c:257)
r7:00000000 r6:8281f77c r5:00000000 r4:82260500
[<80201b08>] (show_stack) from [<8021fb74>] (__dump_stack lib/dump_stack.c:94 [inline])
[<80201b08>] (show_stack) from [<8021fb74>] (dump_stack_lvl+0x54/0x7c lib/dump_stack.c:120)
[<8021fb20>] (dump_stack_lvl) from [<8021fbb4>] (dump_stack+0x18/0x1c lib/dump_stack.c:129)
r5:00000000 r4:82a77d18
[<8021fb9c>] (dump_stack) from [<80202624>] (vpanic+0x10c/0x30c kernel/panic.c:430)
[<80202518>] (vpanic) from [<80202858>] (trace_suspend_resume+0x0/0xd8 kernel/panic.c:566)
r7:826c2080
[<80202824>] (panic) from [<81a3d880>] (schedule_debug kernel/sched/core.c:5918 [inline])
[<80202824>] (panic) from [<81a3d880>] (__schedule+0xf64/0xf68 kernel/sched/core.c:6838)
r3:57ac6e9d r2:00000000 r1:82260500 r0:82251904
[<81a3c91c>] (__schedule) from [<81a3dbd0>] (schedule_idle+0x24/0x68 kernel/sched/core.c:7084)
r10:00000000 r9:00000000 r8:00000000 r7:8280c6d0 r6:8281b240 r5:8280c690
r4:8281b240
[<81a3dbac>] (schedule_idle) from [<802b2984>] (do_idle+0x198/0x2c8 kernel/sched/idle.c:358)
r5:8280c690 r4:00000000
[<802b27ec>] (do_idle) from [<802b2de4>] (cpu_startup_entry+0x30/0x34 kernel/sched/idle.c:428)
r10:8281ad74 r9:8238a790 r8:00000000 r7:8280c640 r6:deffc06c r5:82822078
r4:000000ed
[<802b2db4>] (cpu_startup_entry) from [<81a3abac>] (kernel_init+0x0/0x138 init/main.c:744)
[<81a3aacc>] (rest_init) from [<826012c4>] (start_kernel+0x734/0x750 init/main.c:1097)
[<82600b90>] (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

[syzbot]

Sending this report to the next reporting stage.