[v5.15] kernel panic: Attempted to kill init!

0 views
Skip to first unread message

syzbot

unread,
Jul 24, 2026, 5:50:34 PM (9 hours ago) Jul 24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 674f684f7c61 Linux 5.15.212
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=155132ea580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=13fd732bdff0b3aabf7d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f55be2937b89/disk-674f684f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a19fb0ffc049/vmlinux-674f684f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/365d4529a007/bzImage-674f684f.xz

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

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
CPU: 1 PID: 1 Comm: init Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
panic+0x2f8/0x850 kernel/panic.c:309
do_exit+0x1bdf/0x2110 kernel/exit.c:844
do_group_exit+0x12c/0x2f0 kernel/exit.c:998
get_signal+0x7eb/0x12e0 kernel/signal.c:2901
arch_do_signal_or_restart+0xe6/0x12a0 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:320
exc_page_fault+0x88/0x100 arch/x86/mm/fault.c:1499
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:606
RIP: 0033:0x7f50a0008407
Code: Unable to access opcode bytes at RIP 0x7f50a00083dd.
RSP: 002b:00007ffca6e36b70 EFLAGS: 00010202
RAX: 0000000000000011 RBX: 00007f509feb8c80 RCX: 00007f50a0008407
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007f50a0222498
RBP: 00007f50a0222490 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000202 R12: 00007f50a0222490
R13: 00007ffca6e36bec R14: 00007f50a025a000 R15: 000055bc71c8fd98
</TASK>
Kernel Offset: disabled
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

unread,
Jul 24, 2026, 5:58:42 PM (9 hours ago) Jul 24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: dc5c83b7f5f8 Linux 6.1.178
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15fbe09e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link: https://syzkaller.appspot.com/bug?extid=181812efe47a5faa4481
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/96393e4697a3/disk-dc5c83b7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d4afce44fab/vmlinux-dc5c83b7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4787e310d875/Image-dc5c83b7.gz.xz

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

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
CPU: 0 PID: 1 Comm: init Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
panic+0x2f8/0x7ac kernel/panic.c:339
do_exit+0x1504/0x19ac kernel/exit.c:841
do_group_exit+0x198/0x238 kernel/exit.c:1024
get_signal+0x11f4/0x133c kernel/signal.c:2872
do_signal arch/arm64/kernel/signal.c:1095 [inline]
do_notify_resume+0x2a8/0x2c84 arch/arm64/kernel/signal.c:1148
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_ia+0xe8/0x1d0 arch/arm64/kernel/entry-common.c:534
el0t_64_sync_handler+0xd8/0xf0 arch/arm64/kernel/entry-common.c:661
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0a0000,000f0097,a65bfea7
Memory Limit: none

syzbot

unread,
Jul 24, 2026, 8:26:36 PM (6 hours ago) Jul 24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: da47cbc25466 Linux 6.6.144
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14182499580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0bc3d90c30838b5
dashboard link: https://syzkaller.appspot.com/bug?extid=bda7a5f56e0adc02ccfa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6988639f2873/disk-da47cbc2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/796fa32e7777/vmlinux-da47cbc2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/480ca9c40b5c/bzImage-da47cbc2.xz

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

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
CPU: 0 PID: 1 Comm: init Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
panic+0x2ca/0x720 kernel/panic.c:340
do_exit+0x1ea8/0x2530 kernel/exit.c:844
do_group_exit+0x22d/0x2f0 kernel/exit.c:1026
get_signal+0x12a6/0x1390 kernel/signal.c:2903
arch_do_signal_or_restart+0xc2/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x30 kernel/entry/common.c:315
exc_page_fault+0x8c/0x100 arch/x86/mm/fault.c:1519
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7f0d590e3407
Code: Unable to access opcode bytes at 0x7f0d590e33dd.
RSP: 002b:00007ffd2c707280 EFLAGS: 00010202
RAX: 0000000000000011 RBX: 00007f0d58f93c80 RCX: 00007f0d590e3407
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007f0d592fd498
RBP: 00007f0d592fd490 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000202 R12: 00007f0d592fd490
R13: 00007ffd2c7072fc R14: 00007f0d59335000 R15: 000055baaeb6dd98
</TASK>
Kernel Offset: disabled
Reply all
Reply to author
Forward
0 new messages