linux-kernel - [syzbot] [kernel?] kernel panic: corrupted stack end in smpboot_thread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <00000000000067c0b706225ed4b0@google.com>
Date: Tue, 17 Sep 2024 23:22:26 -0700
From: syzbot <syzbot+c634615db61fdcc74232@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, peterz@...radead.org, 
	syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: [syzbot] [kernel?] kernel panic: corrupted stack end in smpboot_thread_fn

Hello,

syzbot found the following issue on:

HEAD commit:    7c1e5b9690b0 riscv: Disable preemption while handling PR_R..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=1259bfc7980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c79e90d7b2f5b364
dashboard link: https://syzkaller.appspot.com/bug?extid=c634615db61fdcc74232
compiler:       riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: riscv64

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-7c1e5b96.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0f3679bc7f7b/vmlinux-7c1e5b96.xz
kernel image: https://storage.googleapis.com/syzbot-assets/867fc7aa207b/Image-7c1e5b96.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc2-syzkaller-g7c1e5b9690b0 #0
Hardware name: riscv-virtio,qemu (DT)
Call Trace:
[<ffffffff80010216>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:130
[<ffffffff85edbd86>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:136
[<ffffffff85f3735e>] __dump_stack lib/dump_stack.c:93 [inline]
[<ffffffff85f3735e>] dump_stack_lvl+0x108/0x196 lib/dump_stack.c:119
[<ffffffff85f37408>] dump_stack+0x1c/0x24 lib/dump_stack.c:128
[<ffffffff85edc94a>] panic+0x388/0x806 kernel/panic.c:348
[<ffffffff85f4554a>] schedule_debug kernel/sched/core.c:5745 [inline]
[<ffffffff85f4554a>] __schedule+0x3230/0x3288 kernel/sched/core.c:6411
[<ffffffff85f45666>] __schedule_loop kernel/sched/core.c:6606 [inline]
[<ffffffff85f45666>] schedule+0xc4/0x324 kernel/sched/core.c:6621
[<ffffffff801695e0>] smpboot_thread_fn+0x2ea/0xb9c kernel/smpboot.c:160
[<ffffffff8015372c>] kthread+0x28c/0x3a6 kernel/kthread.c:389
[<ffffffff85f5bb82>] ret_from_fork+0xe/0x1c arch/riscv/kernel/entry.S:239
SMP: stopping secondary CPUs
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 syzkaller@...glegroups.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