BUG: unable to handle kernel NULL pointer dereference in vmx_set_msr
Hello, syzbot found the following crash on: HEAD commit:be779f03d563 Merge tag 'kbuild-v4.18-2' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10f9185f80 kernel config: https://syzkaller.appspot.com/x/.config?x=855fb54e1e019da2 dashboard link: https://syzkaller.appspot.com/bug?extid=405a50b23dd790f609b1 compiler: gcc (GCC) 8.0.1 20180413 (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+405a50b23dd790f60...@syzkaller.appspotmail.com BUG: unable to handle kernel NULL pointer dereference at PGD 1890f1067 P4D 1890f1067 PUD 1890f2067 PMD 0 netlink: 8 bytes leftover after parsing attributes in process `syz-executor0'. Oops: 0010 [#1] SMP KASAN CPU: 0 PID: 12381 Comm: syz-executor7 Not tainted 4.17.0+ #101 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010: (null) Code: unchecked MSR access error: WRMSR to 0x49 (tried to write 0x0001) at rIP: 0x81347e18 (native_write_msr+0x8/0x30) Bad RIP value. RSP: 0018:88019151f4c0 EFLAGS: 00010246 RAX: RBX: 8801d2dca800 RCX: 110eac7d RDX: 88019151f9e0 RSI: 8801c922da40 RDI: 8801c4a5a540 RBP: 88019151f630 R08: 0001 R09: Call Trace: R10: R11: R12: 1100322a3e9d R13: 88019151f9e0 R14: 8801d2dca812 R15: 8801d2dcac58 FS: 7f5039c16700() GS:8801dae0() knlGS: CS: 0010 DS: ES: CR0: 80050033 paravirt_write_msr arch/x86/include/asm/paravirt.h:117 [inline] wrmsrl arch/x86/include/asm/paravirt.h:150 [inline] vmx_set_msr+0x19b/0x2010 arch/x86/kvm/vmx.c:3901 CR2: ffd6 CR3: 0001890f CR4: 001426f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: kvm_set_msr+0x18a/0x370 arch/x86/kvm/x86.c:1208 do_set_msr+0x106/0x190 arch/x86/kvm/x86.c:1237 sock_poll+0x1d1/0x710 net/socket.c:1168 vfs_poll+0x77/0x2a0 fs/select.c:40 do_pollfd fs/select.c:848 [inline] do_poll fs/select.c:896 [inline] do_sys_poll+0x6fd/0x1100 fs/select.c:990 __msr_io arch/x86/kvm/x86.c:2784 [inline] msr_io+0x21a/0x360 arch/x86/kvm/x86.c:2820 kvm_arch_vcpu_ioctl+0x14cb/0x36f0 arch/x86/kvm/x86.c:3782 __do_sys_ppoll fs/select.c:1098 [inline] __se_sys_ppoll fs/select.c:1070 [inline] __x64_sys_ppoll+0x2fa/0x5f0 fs/select.c:1070 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x455b29 Code: 1d ba fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 eb b9 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:7f5039c15c68 EFLAGS: 0246 ORIG_RAX: 010f RAX: ffda RBX: 7f5039c166d4 RCX: 00455b29 RDX: 2140 RSI: 0001 RDI: 20c0 RBP: 0072bea0 R08: 0008 R09: R10: 2180 R11: 0246 R12: R13: 004c05f3 R14: 004cfb20 R15: Modules linked in: Dumping ftrace buffer: (ftrace buffer empty) CR2: ---[ end trace 2f889d9e79d87fbd ]--- RIP: 0010: (null) Code: Bad RIP value. RSP: 0018:88019151f4c0 EFLAGS: 00010246 RAX: RBX: 8801d2dca800 RCX: 110eac7d RDX: 88019151f9e0 RSI: 8801c922da40 RDI: 8801c4a5a540 RBP: 88019151f630 R08: 0001 R09: R10: R11: R12: 1100322a3e9d R13: 88019151f9e0 R14: 8801d2dca812 R15: 8801d2dcac58 FS: 7f5039c16700() GS:8801dae0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: ffd6 CR3: 0001890f CR4: 001426f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 --- 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 syzkal...@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot.
BUG: unable to handle kernel NULL pointer dereference in vmx_set_msr
Hello, syzbot found the following crash on: HEAD commit:be779f03d563 Merge tag 'kbuild-v4.18-2' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10f9185f80 kernel config: https://syzkaller.appspot.com/x/.config?x=855fb54e1e019da2 dashboard link: https://syzkaller.appspot.com/bug?extid=405a50b23dd790f609b1 compiler: gcc (GCC) 8.0.1 20180413 (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+405a50b23dd790f60...@syzkaller.appspotmail.com BUG: unable to handle kernel NULL pointer dereference at PGD 1890f1067 P4D 1890f1067 PUD 1890f2067 PMD 0 netlink: 8 bytes leftover after parsing attributes in process `syz-executor0'. Oops: 0010 [#1] SMP KASAN CPU: 0 PID: 12381 Comm: syz-executor7 Not tainted 4.17.0+ #101 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010: (null) Code: unchecked MSR access error: WRMSR to 0x49 (tried to write 0x0001) at rIP: 0x81347e18 (native_write_msr+0x8/0x30) Bad RIP value. RSP: 0018:88019151f4c0 EFLAGS: 00010246 RAX: RBX: 8801d2dca800 RCX: 110eac7d RDX: 88019151f9e0 RSI: 8801c922da40 RDI: 8801c4a5a540 RBP: 88019151f630 R08: 0001 R09: Call Trace: R10: R11: R12: 1100322a3e9d R13: 88019151f9e0 R14: 8801d2dca812 R15: 8801d2dcac58 FS: 7f5039c16700() GS:8801dae0() knlGS: CS: 0010 DS: ES: CR0: 80050033 paravirt_write_msr arch/x86/include/asm/paravirt.h:117 [inline] wrmsrl arch/x86/include/asm/paravirt.h:150 [inline] vmx_set_msr+0x19b/0x2010 arch/x86/kvm/vmx.c:3901 CR2: ffd6 CR3: 0001890f CR4: 001426f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: kvm_set_msr+0x18a/0x370 arch/x86/kvm/x86.c:1208 do_set_msr+0x106/0x190 arch/x86/kvm/x86.c:1237 sock_poll+0x1d1/0x710 net/socket.c:1168 vfs_poll+0x77/0x2a0 fs/select.c:40 do_pollfd fs/select.c:848 [inline] do_poll fs/select.c:896 [inline] do_sys_poll+0x6fd/0x1100 fs/select.c:990 __msr_io arch/x86/kvm/x86.c:2784 [inline] msr_io+0x21a/0x360 arch/x86/kvm/x86.c:2820 kvm_arch_vcpu_ioctl+0x14cb/0x36f0 arch/x86/kvm/x86.c:3782 __do_sys_ppoll fs/select.c:1098 [inline] __se_sys_ppoll fs/select.c:1070 [inline] __x64_sys_ppoll+0x2fa/0x5f0 fs/select.c:1070 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x455b29 Code: 1d ba fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 eb b9 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:7f5039c15c68 EFLAGS: 0246 ORIG_RAX: 010f RAX: ffda RBX: 7f5039c166d4 RCX: 00455b29 RDX: 2140 RSI: 0001 RDI: 20c0 RBP: 0072bea0 R08: 0008 R09: R10: 2180 R11: 0246 R12: R13: 004c05f3 R14: 004cfb20 R15: Modules linked in: Dumping ftrace buffer: (ftrace buffer empty) CR2: ---[ end trace 2f889d9e79d87fbd ]--- RIP: 0010: (null) Code: Bad RIP value. RSP: 0018:88019151f4c0 EFLAGS: 00010246 RAX: RBX: 8801d2dca800 RCX: 110eac7d RDX: 88019151f9e0 RSI: 8801c922da40 RDI: 8801c4a5a540 RBP: 88019151f630 R08: 0001 R09: R10: R11: R12: 1100322a3e9d R13: 88019151f9e0 R14: 8801d2dca812 R15: 8801d2dcac58 FS: 7f5039c16700() GS:8801dae0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: ffd6 CR3: 0001890f CR4: 001426f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 --- 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 syzkal...@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot.
