BUG: unable to handle kernel NULL pointer dereference in __traceiter_sys_enter

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 76c057c8 Merge branch 'parisc-5.11-2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1086f978d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f95f6da2ec0c48fd
dashboard link: https://syzkaller.appspot.com/bug?extid=8fcdb44f953663cac87c
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]

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

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

BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 64a95067 P4D 64a95067 PUD 64a96067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 3 PID: 11200 Comm: syz-executor.3 Not tainted 5.11.0-rc5-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
RIP: 0010:__traceiter_sys_enter+0x11/0x40 include/trace/events/syscalls.h:18
Code: 8b 1d b3 ac bd 0d 31 ff 48 89 de e8 f9 ac 11 00 48 85 db 5b 0f 95 c0 c3 cc 41 54 49 89 f4 55 48 89 d5 53 48 8b 1d 6f d0 8e 0b <48> 8b 03 48 8b 7b 08 48 83 c3 18 48 89 ea 4c 89 e6 ff d0 48 8b 03
RSP: 0018:ffffc90001097ef8 EFLAGS: 00010286
RAX: ffff88801f560790 RBX: 0000000000000000 RCX: 1ffffffff1a06e91
RDX: 000000000000004e RSI: ffffc90001097f58 RDI: ffffc90000682000
RBP: 000000000000004e R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff81789718 R11: 0000000000000000 R12: ffffc90001097f58
R13: 000000000000004e R14: 000000000000004e R15: 0000000000000000
FS: 0000000002d0e940(0000) GS:ffff88802cd00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000064a94000 CR4: 0000000000150ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_sys_enter include/trace/events/syscalls.h:18 [inline]
syscall_trace_enter.constprop.0+0x20d/0x260 kernel/entry/common.c:76
do_syscall_64+0xf/0x70 arch/x86/entry/common.c:41
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45c1bb
Code: 41 5d c3 64 41 83 3c 24 02 74 b6 31 d2 eb b9 41 57 41 56 48 63 ff 41 55 41 54 b8 4e 00 00 00 55 53 48 89 f3 48 83 ec 08 0f 05 <48> 3d 00 f0 ff ff 77 55 48 8d 2c 06 49 89 c4 48 39 ee 73 34 90 44
RSP: 002b:00007ffdd1cb59d0 EFLAGS: 00000202 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 0000000002d0fa90 RCX: 000000000045c1bb
RDX: 0000000000008000 RSI: 0000000002d0fa90 RDI: 0000000000000003
RBP: 0000000002d0fa90 R08: 0000000000000003 R09: 0000000000008040
R10: 0000000000000000 R11: 0000000000000202 R12: ffffffffffffffd4
R13: 0000000000000016 R14: 0000000000000032 R15: 000000000003ce07
Modules linked in:
CR2: 0000000000000000
---[ end trace 4d56709ed2f5b624 ]---
RIP: 0010:__traceiter_sys_enter+0x11/0x40 include/trace/events/syscalls.h:18
Code: 8b 1d b3 ac bd 0d 31 ff 48 89 de e8 f9 ac 11 00 48 85 db 5b 0f 95 c0 c3 cc 41 54 49 89 f4 55 48 89 d5 53 48 8b 1d 6f d0 8e 0b <48> 8b 03 48 8b 7b 08 48 83 c3 18 48 89 ea 4c 89 e6 ff d0 48 8b 03
RSP: 0018:ffffc90001097ef8 EFLAGS: 00010286
RAX: ffff88801f560790 RBX: 0000000000000000 RCX: 1ffffffff1a06e91
RDX: 000000000000004e RSI: ffffc90001097f58 RDI: ffffc90000682000
RBP: 000000000000004e R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff81789718 R11: 0000000000000000 R12: ffffc90001097f58
R13: 000000000000004e R14: 000000000000004e R15: 0000000000000000
FS: 0000000002d0e940(0000) GS:ffff88802cd00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000064a94000 CR4: 0000000000150ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.