[moderation] [netfilter?] kernel panic: stack is corrupted in __kmalloc_node

3 views
Skip to first unread message

syzbot

unread,
Feb 8, 2024, 8:08:27 AMFeb 8
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6613476e225e Linux 6.8-rc1
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=14e2f5ffe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=877e61347079aad5
dashboard link: https://syzkaller.appspot.com/bug?extid=c498b4e65232cdb1e37c
compiler: riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: riscv64
CC: [f...@strlen.de kad...@netfilter.org linux-...@vger.kernel.org net...@vger.kernel.org netfilt...@vger.kernel.org pa...@netfilter.org]

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-6613476e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/33ea806d02dd/vmlinux-6613476e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/33195f72f823/Image-6613476e.xz

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

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __kmalloc_node+0x434/0x434 mm/slub.c:3989
CPU: 0 PID: 13403 Comm: kworker/u5:5 Not tainted 6.8.0-rc1-syzkaller #0
Hardware name: riscv-virtio,qemu (DT)
Workqueue: events_unbound call_usermodehelper_exec_work
Call Trace:
[<ffffffff80010868>] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:121
[<ffffffff858a9b60>] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:127
[<ffffffff85904e9c>] __dump_stack lib/dump_stack.c:88 [inline]
[<ffffffff85904e9c>] dump_stack_lvl+0xe8/0x154 lib/dump_stack.c:106
[<ffffffff85904f24>] dump_stack+0x1c/0x24 lib/dump_stack.c:113
[<ffffffff858aa5b2>] panic+0x33c/0x77a kernel/panic.c:344
[<ffffffff859071e6>] warn_bogus_irq_restore+0x0/0x38 kernel/panic.c:763
[<ffffffff8080e2ae>] __kmalloc+0x0/0x40c mm/slub.c:3989
[<ffffffff807e6318>] kmalloc_node include/linux/slab.h:610 [inline]
[<ffffffff807e6318>] __vmalloc_area_node mm/vmalloc.c:3125 [inline]
[<ffffffff807e6318>] __vmalloc_node_range+0x37a/0x1316 mm/vmalloc.c:3320
[<ffffffff800afe58>] alloc_thread_stack_node kernel/fork.c:307 [inline]
[<ffffffff800afe58>] dup_task_struct kernel/fork.c:1112 [inline]
[<ffffffff800afe58>] copy_process+0x2c2a/0x6b54 kernel/fork.c:2326
[<ffffffff800b3fae>] kernel_clone+0x11e/0xa16 kernel/fork.c:2901
[<ffffffff800b4f3c>] user_mode_thread+0xea/0x11a kernel/fork.c:2979
[<ffffffff80115dec>] call_usermodehelper_exec_work kernel/umh.c:172 [inline]
[<ffffffff80115dec>] call_usermodehelper_exec_work+0xd4/0x1ac kernel/umh.c:158
[<ffffffff801231ea>] process_one_work+0x7ce/0x179c kernel/workqueue.c:2633
[<ffffffff80124c94>] process_scheduled_works kernel/workqueue.c:2706 [inline]
[<ffffffff80124c94>] worker_thread+0xadc/0x10f8 kernel/workqueue.c:2787
[<ffffffff80144154>] kthread+0x28c/0x3a6 kernel/kthread.c:388
[<ffffffff85928722>] ret_from_fork+0xe/0x1c arch/riscv/kernel/entry.S:229
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 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
Reply all
Reply to author
Forward
0 new messages