============================= WARNING: suspicious RCU usage syzkaller #0 Not tainted ----------------------------- include/linux/kvm_host.h:889 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.0.17/5091: #0: ffff88807b63c0c8 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d2/0xc10 virt/kvm/kvm_main.c:3871 stack backtrace: CPU: 1 PID: 5091 Comm: syz.0.17 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 __kvm_memslots include/linux/kvm_host.h:887 [inline] kvm_vcpu_memslots+0x1b6/0x200 include/linux/kvm_host.h:901 kvm_vcpu_gfn_to_memslot+0x2b/0x3c0 virt/kvm/kvm_main.c:2158 kvm_vcpu_unmap+0x5b/0x80 virt/kvm/kvm_main.c:2773 nested_vmx_vmexit+0x1447/0x2910 arch/x86/kvm/vmx/nested.c:4676 vmx_check_nested_events+0x4e5/0x2390 arch/x86/kvm/vmx/nested.c:3941 kvm_apic_accept_events+0x136/0x560 arch/x86/kvm/lapic.c:2932 kvm_arch_vcpu_ioctl_get_mpstate+0x57/0x1b0 arch/x86/kvm/x86.c:10608 kvm_vcpu_ioctl+0x589/0xc10 virt/kvm/kvm_main.c:3956 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f3df6c23379 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3df6245028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f3df6e6f180 RCX: 00007f3df6c23379 RDX: 0000000000000000 RSI: 000000008004ae98 RDI: 0000000000000005 RBP: 00007f3df6cb6d68 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f3df6e6f218 R14: 00007f3df6e6f180 R15: 00007fff5b099348