[v5.15] WARNING in vmx_queue_exception

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d214f240b0f6 Linux 5.15.100
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12dbaa1ac80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5c5a36ceb954515
dashboard link: https://syzkaller.appspot.com/bug?extid=4d82a15086e9913d0e1a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4e12037285d4/disk-d214f240.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/929d982226d5/vmlinux-d214f240.xz
kernel image: https://storage.googleapis.com/syzbot-assets/59140c032c99/bzImage-d214f240.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4d82a1...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 11178 at arch/x86/kvm/vmx/vmx.c:1703 vmx_queue_exception+0x2d2/0x480
Modules linked in:
CPU: 1 PID: 11178 Comm: syz-executor.3 Not tainted 5.15.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:vmx_queue_exception+0x2d2/0x480 arch/x86/kvm/vmx/vmx.c:1703
Code: 9e 01 00 00 e8 bf 6d 5d 00 eb 0c e8 b8 6d 5d 00 eb 05 e8 b1 6d 5d 00 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f c3 e8 9e 6d 5d 00 <0f> 0b e9 a2 fe ff ff 89 f9 80 e1 07 38 c1 0f 8c 55 fd ff ff e8 95
RSP: 0018:ffffc90002f6f558 EFLAGS: 00010287
RAX: ffffffff81230ce2 RBX: 0000000000000001 RCX: 0000000000040000
RDX: ffffc90004289000 RSI: 0000000000000447 RDI: 0000000000000448
RBP: ffffc90002f6fc50 R08: ffffffff81230b7e R09: fffffbfff1bc70f6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880593a8000
R13: dffffc0000000000 R14: 0000000000000003 R15: 0000000080000003
FS: 00007f56dcbc1700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4701a3f1b8 CR3: 0000000078f0f000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000006
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inject_pending_event arch/x86/kvm/x86.c:9194 [inline]
vcpu_enter_guest+0x1c4f/0x99c0 arch/x86/kvm/x86.c:9852
vcpu_run arch/x86/kvm/x86.c:10105 [inline]
kvm_arch_vcpu_ioctl_run+0xa68/0x1e70 arch/x86/kvm/x86.c:10337
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3843
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f56de64f0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f56dcbc1168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f56de76ef80 RCX: 00007f56de64f0f9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005
RBP: 00007f56de6aaae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd2deefb4f R14: 00007f56dcbc1300 R15: 0000000000022000
</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 syzk...@googlegroups.com.

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f59bfac80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c4a69039b8408b46

dashboard link: https://syzkaller.appspot.com/bug?extid=4d82a15086e9913d0e1a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137c55c6c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11ab9724c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/20c511f4e9f8/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/af0889244076/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25bcdac064d7/bzImage-bbf9f29b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4d82a1...@syzkaller.appspotmail.com

L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3585 at arch/x86/kvm/vmx/vmx.c:1703 vmx_queue_exception+0x2d2/0x480
Modules linked in:
CPU: 0 PID: 3585 Comm: syz-executor358 Not tainted 5.15.101-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:vmx_queue_exception+0x2d2/0x480 arch/x86/kvm/vmx/vmx.c:1703
Code: 9e 01 00 00 e8 bf 6d 5d 00 eb 0c e8 b8 6d 5d 00 eb 05 e8 b1 6d 5d 00 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f c3 e8 9e 6d 5d 00 <0f> 0b e9 a2 fe ff ff 89 f9 80 e1 07 38 c1 0f 8c 55 fd ff ff e8 95

RSP: 0018:ffffc9000302f558 EFLAGS: 00010293
RAX: ffffffff81230ce2 RBX: 0000000000000001 RCX: ffff88807d789d00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000302fc50 R08: ffffffff81230b7e R09: fffffbfff1bc70f6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807962c000

R13: dffffc0000000000 R14: 0000000000000003 R15: 0000000080000003

FS: 0000555556025300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 000055ff026d8b00 CR3: 000000007487d000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Call Trace:
<TASK>
inject_pending_event arch/x86/kvm/x86.c:9194 [inline]
vcpu_enter_guest+0x1c4f/0x99c0 arch/x86/kvm/x86.c:9852
vcpu_run arch/x86/kvm/x86.c:10105 [inline]
kvm_arch_vcpu_ioctl_run+0xa68/0x1e70 arch/x86/kvm/x86.c:10337
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3843
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb

RIP: 0033:0x7f6d136b3f79
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffed09f5998 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6d136b3f79

RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000005

RBP: 00007f6d13677a70 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6d13677b00
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit fc4fad79fc3d8841562e2a85808079da5b4835f6
git tree: upstream
Author: Sean Christopherson <sea...@google.com>
Date: Tue Dec 28 23:24:36 2021 +0000

KVM: VMX: Reject KVM_RUN if emulation is required with pending exception

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16b84553a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f83fab0469f5de7
dashboard link: https://syzkaller.appspot.com/bug?extid=4d82a15086e9913d0e1a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e6050dc80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173f876dc80000


Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection