kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: 0000 [#1] SMP KASAN CPU: 0 PID: 10837 Comm: syz-executor5 Not tainted 4.18.0-rc5+ #154 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:msr_write_intercepted arch/x86/kvm/vmx.c:2338 [inline] RIP: 0010:vmx_vcpu_run+0x1328/0x2600 arch/x86/kvm/vmx.c:10184 FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 Code: 91 00 00 00 e8 89 cd 5c 00 48 8b 54 24 08 48 b8 00 00 00 00 00 CPU: 1 PID: 10878 Comm: syz-executor2 Not tainted 4.18.0-rc5+ #154 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 fc ff Call Trace: df __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 48 c1 fail_dump lib/fault-inject.c:51 [inline] should_fail.cold.4+0xa/0x1a lib/fault-inject.c:149 ea 03 80 3c 02 00 0f 85 8c 10 00 00 48 8b 04 24 <48> 8b 98 40 57 00 00 48 __should_failslab+0x124/0x180 mm/failslab.c:32 b8 should_failslab+0x9/0x14 mm/slab_common.c:1557 00 slab_pre_alloc_hook mm/slab.h:423 [inline] slab_alloc mm/slab.c:3378 [inline] kmem_cache_alloc+0x2af/0x760 mm/slab.c:3552 00 00 00 00 kmem_cache_zalloc include/linux/slab.h:697 [inline] mmu_topup_memory_cache arch/x86/kvm/mmu.c:865 [inline] mmu_topup_memory_caches+0x2fa/0x3a0 arch/x86/kvm/mmu.c:918 fc kvm_mmu_load+0x21/0x10e0 arch/x86/kvm/mmu.c:4656 ff kvm_mmu_reload arch/x86/kvm/mmu.h:85 [inline] vcpu_enter_guest+0x3aa6/0x6090 arch/x86/kvm/x86.c:7390 df 48 8d 7b 40 48 RSP: 0018:ffff8801a2d27370 EFLAGS: 00010046 ================================================================== BUG: KASAN: stack-out-of-bounds in __show_regs.cold.7+0x2b/0x54a arch/x86/kernel/process_64.c:79 Read of size 8 at addr ffff8801a2d27320 by task syz-executor5/10837 vcpu_run arch/x86/kvm/x86.c:7587 [inline] kvm_arch_vcpu_ioctl_run+0x33e/0x1690 arch/x86/kvm/x86.c:7764 kvm_vcpu_ioctl+0x7b8/0x1300 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2580 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:684 ksys_ioctl+0xa9/0xd0 fs/ioctl.c:701 __do_sys_ioctl fs/ioctl.c:708 [inline] __se_sys_ioctl fs/ioctl.c:706 [inline] __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:706 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x455ab9 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:00007f960e1d5c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f960e1d66d4 RCX: 0000000000455ab9 RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000016 RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000017 R13: 00000000004bdc94 R14: 00000000004cc6d0 R15: 000000000000005a CPU: 0 PID: 10837 Comm: syz-executor5 Not tainted 4.18.0-rc5+ #154 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: The buggy address belongs to the page: page:ffffea00068b49c0 count:0 mapcount:0 mapping:0000000000000000 index:0x0 flags: 0x2fffc0000000000() raw: 02fffc0000000000 0000000000000000 ffffffff06340101 0000000000000000 raw: 0000000000000000 ffff8801b0163dc0 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8801a2d27200: 00 00 00 00 00 00 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 ffff8801a2d27280: f2 f2 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 >ffff8801a2d27300: f2 f2 f8 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 ^ ffff8801a2d27380: 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2 f2 f2 f2 f2 ffff8801a2d27400: 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 00 00 ==================================================================