BUG: unable to handle kernel NULL pointer dereference in do_syscall_64 (2)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 4520f06b Linux 4.14.175
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=104d9253e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=93cf891381c0c347
dashboard link: https://syzkaller.appspot.com/bug?extid=056f5d610ea3fcaa0b46
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

BUG: unable to handle kernel NULL pointer dereference
kasan: CONFIG_KASAN_INLINE enabled
at (null)
kasan: GPF could be caused by NULL-ptr deref or user memory access
IP: do_syscall_64+0x1e3/0x640 arch/x86/entry/common.c:292
PGD 97e08067 P4D 97e08067 PUD 5024b067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 23448 Comm: syz-executor.1 Not tainted 4.14.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88804f20e500 task.stack: ffff88804b430000
RIP: 0010:do_syscall_64+0x1e3/0x640 arch/x86/entry/common.c:292
RSP: 0018:ffff88804b437f00 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffffff814e0900 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88804b437fa8
RBP: ffff88804b437f58 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff87d16698
R13: ffff88804b437fd0 R14: ffff88804f20e500 R15: 0000000000000000
FS: 00000000012c0940(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000008c29a000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
entry_SYSCALL_64_after_hwframe+0x42/0xb7
invalid opcode: 0000 [#2] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 23448 Comm: syz-executor.1 Not tainted 4.14.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88804f20e500 task.stack: ffff88804b430000
RIP: 0010:warn_bad_vsyscall arch/x86/entry/vsyscall/vsyscall_64.c:79 [inline]
RIP: 0010:warn_bad_vsyscall.cold+0x39/0x189 arch/x86/entry/vsyscall/vsyscall_64.c:73
RSP: 0018:ffff88804b437560 EFLAGS: 00010096
RAX: ffff88804f20e500 RBX: 1ffff11009686eb5 RCX: ffff88804b43759f
RDX: 0000000000000000 RSI: ffff88804b437608 RDI: 000000000045ad51
RBP: 000000000045ad51 R08: ffff88804b437690 R09: fffffbfff14a8d5a
R10: fffffbfff14a8d59 R11: ffffffff8a546acb R12: ffff88804b437690
R13: ffff88804b4375c8 R14: ffff88804b437608 R15: ffff88804b4375e8
FS: 00000000012c0940(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000008c29a000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2a 48 c1 <ea> 03 80 3c 02 00 74 05 e8 b0 ef 82 00 48 8d 7b 50 b8 ff ff 37
RIP: warn_bad_vsyscall arch/x86/entry/vsyscall/vsyscall_64.c:79 [inline] RSP: ffff88804b437560
RIP: warn_bad_vsyscall.cold+0x39/0x189 arch/x86/entry/vsyscall/vsyscall_64.c:73 RSP: ffff88804b437560
---[ end trace 190e7ea3e2a17b78 ]---


---
This bug 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 bug report. 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.