Hello,
syzbot found the following issue on:
HEAD commit: 12952a23a5da Linux 5.15.137
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16bd391d680000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fec74236cf840914
dashboard link:
https://syzkaller.appspot.com/bug?extid=f71fb831af7a7dffea27
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=124bbcc7680000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7e2dc2318d41/disk-12952a23.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/753b1c98a896/vmlinux-12952a23.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/2ed1ab0d1e32/bzImage-12952a23.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f71fb8...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000011: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f]
CPU: 0 PID: 3656 Comm: syz-executor.5 Not tainted 5.15.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:inherit_group kernel/events/core.c:13280 [inline]
RIP: 0010:inherit_task_group+0x276/0x710 kernel/events/core.c:13327
Code: 81 c3 8c 00 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 3a 04 00 00 8b 1b 49 81 c6 8c 00 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 3a 04 00 00 41 89 1e e9 98 fe ff ff e8
RSP: 0018:ffffc900035af8f0 EFLAGS: 00010207
RAX: 0000000000000011 RBX: 0000000000000000 RCX: ffff888022221dc0
RDX: 0000000000000000 RSI: ffffffff8a8b0be0 RDI: ffff88813fe6f610
RBP: ffff88813fe6f590 R08: dffffc0000000000 R09: fffffbfff1f79a41
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888021f41dc0 R14: 000000000000008c R15: ffff88813fe6f590
FS: 00007f05f0aae6c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f05f0a8dd58 CR3: 000000001a5d7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
perf_event_init_context kernel/events/core.c:13396 [inline]
perf_event_init_task+0x355/0x7a0 kernel/events/core.c:13449
copy_process+0x1570/0x3ef0 kernel/fork.c:2180
kernel_clone+0x210/0x960 kernel/fork.c:2604
__do_sys_clone kernel/fork.c:2721 [inline]
__se_sys_clone kernel/fork.c:2705 [inline]
__x64_sys_clone+0x23f/0x290 kernel/fork.c:2705
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f05f174dae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f05f0aae078 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007f05f186d050 RCX: 00007f05f174dae9
RDX: 0000000000000000 RSI: 0000000001000000 RDI: 00000000c0920400
RBP: 00007f05f179947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000006e R14: 00007f05f186d050 R15: 00007ffd2c93dcc8
</TASK>
Modules linked in:
---[ end trace 1e3d01613877a0ab ]---
RIP: 0010:inherit_group kernel/events/core.c:13280 [inline]
RIP: 0010:inherit_task_group+0x276/0x710 kernel/events/core.c:13327
Code: 81 c3 8c 00 00 00 48 89 d8 48 c1 e8 03 42 0f b6 04 20 84 c0 0f 85 3a 04 00 00 8b 1b 49 81 c6 8c 00 00 00 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 20 84 c0 0f 85 3a 04 00 00 41 89 1e e9 98 fe ff ff e8
RSP: 0018:ffffc900035af8f0 EFLAGS: 00010207
RAX: 0000000000000011 RBX: 0000000000000000 RCX: ffff888022221dc0
RDX: 0000000000000000 RSI: ffffffff8a8b0be0 RDI: ffff88813fe6f610
RBP: ffff88813fe6f590 R08: dffffc0000000000 R09: fffffbfff1f79a41
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888021f41dc0 R14: 000000000000008c R15: ffff88813fe6f590
FS: 00007f05f0aae6c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555659f938 CR3: 000000001a5d7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 81 c3 8c 00 00 00 add $0x8c,%ebx
6: 48 89 d8 mov %rbx,%rax
9: 48 c1 e8 03 shr $0x3,%rax
d: 42 0f b6 04 20 movzbl (%rax,%r12,1),%eax
12: 84 c0 test %al,%al
14: 0f 85 3a 04 00 00 jne 0x454
1a: 8b 1b mov (%rbx),%ebx
1c: 49 81 c6 8c 00 00 00 add $0x8c,%r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 20 movzbl (%rax,%r12,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 3a 04 00 00 jne 0x471
37: 41 89 1e mov %ebx,(%r14)
3a: e9 98 fe ff ff jmp 0xfffffed7
3f: e8 .byte 0xe8
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup