KASAN: vmalloc-out-of-bounds Read in __call_srcu

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: dc56c5ac Merge tag 'platform-drivers-x86-v5.7-2' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e06f4c100000
kernel config: https://syzkaller.appspot.com/x/.config?x=b0212dbee046bc1f
dashboard link: https://syzkaller.appspot.com/bug?extid=f4064b181bcfd1e53bea
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
userspace arch: i386
CC: [b...@alien8.de h...@zytor.com jmat...@google.com jo...@8bytes.org k...@vger.kernel.org linux-...@vger.kernel.org mi...@redhat.com pbon...@redhat.com sean.j.chr...@intel.com tg...@linutronix.de vkuz...@redhat.com wanp...@tencent.com x...@kernel.org]

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+f4064b...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: vmalloc-out-of-bounds in __lock_acquire+0x3fa6/0x4c50 kernel/locking/lockdep.c:4225
Read of size 8 at addr ffffc9001ac3a9a0 by task syz-executor.2/22965

CPU: 1 PID: 22965 Comm: syz-executor.2 Not tainted 5.7.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x188/0x20d lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x315 mm/kasan/report.c:382
__kasan_report.cold+0x35/0x4d mm/kasan/report.c:511
kasan_report+0x33/0x50 mm/kasan/common.c:625
__lock_acquire+0x3fa6/0x4c50 kernel/locking/lockdep.c:4225
lock_acquire+0x1f2/0x8f0 kernel/locking/lockdep.c:4934
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xbf kernel/locking/spinlock.c:159
srcu_funnel_gp_start kernel/rcu/srcutree.c:643 [inline]
__call_srcu kernel/rcu/srcutree.c:872 [inline]
__call_srcu+0x54e/0xd40 kernel/rcu/srcutree.c:835
__synchronize_srcu+0x19d/0x260 kernel/rcu/srcutree.c:921
kvm_arch_destroy_vm+0x3e2/0x510 arch/x86/kvm/x86.c:9913
kvm_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:749 [inline]
kvm_dev_ioctl_create_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:3817 [inline]
kvm_dev_ioctl+0xf6c/0x1490 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3869
__do_compat_sys_ioctl fs/ioctl.c:865 [inline]
__se_compat_sys_ioctl fs/ioctl.c:816 [inline]
__ia32_compat_sys_ioctl+0x23d/0x2b0 fs/ioctl.c:816
do_syscall_32_irqs_on arch/x86/entry/common.c:337 [inline]
do_fast_syscall_32+0x270/0xe90 arch/x86/entry/common.c:396
entry_SYSENTER_compat+0x70/0x7f arch/x86/entry/entry_64_compat.S:139


Memory state around the buggy address:
ffffc9001ac3a880: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
ffffc9001ac3a900: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
>ffffc9001ac3a980: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
^
ffffc9001ac3aa00: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
ffffc9001ac3aa80: f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9 f9
==================================================================


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