[syzbot] [kvm?] WARNING in vmx_handle_exit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    480e035fc4c7 Merge tag 'drm-next-2024-03-13' of https://gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=148aa5e5180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e5b814e91787669
dashboard link: https://syzkaller.appspot.com/bug?extid=988d9efcdf137bc05f66
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=157a2f45180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16126855180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5f73b6ef963d/disk-480e035f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46c949396aad/vmlinux-480e035f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e3b4d0f5a5f8/bzImage-480e035f.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+988d9efcdf137bc05f66@xxxxxxxxxxxxxxxxxxxxxxxxx

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5391 at arch/x86/kvm/vmx/vmx.c:6436 __vmx_handle_exit arch/x86/kvm/vmx/vmx.c:6436 [inline]
WARNING: CPU: 0 PID: 5391 at arch/x86/kvm/vmx/vmx.c:6436 vmx_handle_exit+0x14dc/0x1f40 arch/x86/kvm/vmx/vmx.c:6593
Modules linked in:
CPU: 0 PID: 5391 Comm: syz-executor617 Not tainted 6.8.0-syzkaller-08073-g480e035fc4c7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__vmx_handle_exit arch/x86/kvm/vmx/vmx.c:6436 [inline]
RIP: 0010:vmx_handle_exit+0x14dc/0x1f40 arch/x86/kvm/vmx/vmx.c:6593
Code: 00 00 e8 47 53 6d 00 4c 89 f7 e8 ef da f1 ff 41 bf 01 00 00 00 e9 b1 ed ff ff e8 2f 53 6d 00 e9 45 f4 ff ff e8 25 53 6d 00 90 <0f> 0b 90 42 80 7c 25 00 00 74 08 4c 89 f7 e8 31 a2 d0 00 49 8b 2e
RSP: 0018:ffffc9000595f418 EFLAGS: 00010293
RAX: ffffffff8127a22b RBX: 0000000000000000 RCX: ffff888024ba0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffff1100f531518 R08: ffffffff81278fba R09: 1ffffffff259c2ba
R10: dffffc0000000000 R11: fffffbfff259c2bb R12: dffffc0000000000
R13: ffff88807a98cb90 R14: ffff88807a98a8c0 R15: 0000000080000021
FS:  00007f84df9ff6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000015efe000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vcpu_enter_guest arch/x86/kvm/x86.c:11080 [inline]
 vcpu_run+0x5ca0/0x8790 arch/x86/kvm/x86.c:11184
 kvm_arch_vcpu_ioctl_run+0xa7e/0x1920 arch/x86/kvm/x86.c:11410
 kvm_vcpu_ioctl+0x7f5/0xd00 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4447
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890
 do_syscall_64+0xfb/0x240
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7f84e0287289
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 1d 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f84df9ff218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000000003f RCX: 00007f84e0287289
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00007f84e031d038 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f84e031d030
R13: 00007f84e031d03c R14: 00007f84e02d74f8 R15: 6d766b2f7665642f
 </TASK>


---
This report 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 syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup