[v6.1] WARNING in handle_exception_nmi

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a343b0dd87b4 Linux 6.1.30
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e75f51280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5265a3c898f3cbbb
dashboard link: https://syzkaller.appspot.com/bug?extid=7c737a13057526185ef5
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/195d974b1f1c/disk-a343b0dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea41850547fb/vmlinux-a343b0dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13ec9e70ad28/bzImage-a343b0dd.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5212 at arch/x86/kvm/vmx/vmx.c:5163 handle_exception_nmi+0x8f2/0xe10
Modules linked in:
CPU: 0 PID: 5212 Comm: syz-executor.3 Not tainted 6.1.30-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:handle_exception_nmi+0x8f2/0xe10 arch/x86/kvm/vmx/vmx.c:5163
Code: 64 d1 65 00 0f 0b e9 44 f9 ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 7c f7 ff ff e8 78 18 bc 00 e9 72 f7 ff ff e8 3e d1 65 00 <0f> 0b e9 53 fc ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 9d f8 ff
RSP: 0018:ffffc9000af9f490 EFLAGS: 00010283
RAX: ffffffff8123f432 RBX: ffff888077428000 RCX: 0000000000040000
RDX: ffffc9000b6d2000 RSI: 000000000000a60c RDI: 000000000000a60d
RBP: 0000000000000000 R08: ffffffff8123f07f R09: ffffed100ee8504a
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100ee8501b
R13: 0000000000000000 R14: 0000000030000064 R15: dffffc0000000000
FS: 00007f3f6210d700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000030000012 CR3: 000000007571c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__vmx_handle_exit arch/x86/kvm/vmx/vmx.c:6480 [inline]
vmx_handle_exit+0xca0/0x1a00 arch/x86/kvm/vmx/vmx.c:6497
vcpu_enter_guest+0x2a93/0xa530 arch/x86/kvm/x86.c:10917
vcpu_run arch/x86/kvm/x86.c:11020 [inline]
kvm_arch_vcpu_ioctl_run+0xf5f/0x20c0 arch/x86/kvm/x86.c:11241
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4091
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
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+0x63/0xcd
RIP: 0033:0x7f3f6148c169
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:00007f3f6210d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f3f615abf80 RCX: 00007f3f6148c169
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006
RBP: 00007f3f614e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffed9defd6f R14: 00007f3f6210d300 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.

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

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

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

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: a343b0dd87b4 Linux 6.1.30
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=114a93b9280000

kernel config: https://syzkaller.appspot.com/x/.config?x=5265a3c898f3cbbb
dashboard link: https://syzkaller.appspot.com/bug?extid=7c737a13057526185ef5
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=1202f269280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14873bb9280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/195d974b1f1c/disk-a343b0dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea41850547fb/vmlinux-a343b0dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13ec9e70ad28/bzImage-a343b0dd.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7c737a...@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: 3537 at arch/x86/kvm/vmx/vmx.c:5163 handle_exception_nmi+0x8f2/0xe10
Modules linked in:
CPU: 1 PID: 3537 Comm: syz-executor244 Not tainted 6.1.30-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:handle_exception_nmi+0x8f2/0xe10 arch/x86/kvm/vmx/vmx.c:5163
Code: 64 d1 65 00 0f 0b e9 44 f9 ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 7c f7 ff ff e8 78 18 bc 00 e9 72 f7 ff ff e8 3e d1 65 00 <0f> 0b e9 53 fc ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 9d f8 ff

RSP: 0018:ffffc90003a4f490 EFLAGS: 00010293
RAX: ffffffff8123f432 RBX: ffff88807cf68000 RCX: ffff888016bc1dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff8123f07f R09: ffffed100f9ed04a
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100f9ed01b

R13: 0000000000000000 R14: 0000000030000064 R15: dffffc0000000000

FS: 0000555557416300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000

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

CR2: 0000000030000012 CR3: 00000000209ce000 CR4: 00000000003526e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__vmx_handle_exit arch/x86/kvm/vmx/vmx.c:6480 [inline]
vmx_handle_exit+0xca0/0x1a00 arch/x86/kvm/vmx/vmx.c:6497
vcpu_enter_guest+0x2a93/0xa530 arch/x86/kvm/x86.c:10917
vcpu_run arch/x86/kvm/x86.c:11020 [inline]
kvm_arch_vcpu_ioctl_run+0xf5f/0x20c0 arch/x86/kvm/x86.c:11241
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4091
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
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+0x63/0xcd

RIP: 0033:0x7efefff1f3e9
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:00007ffcf37e3458 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007efefff1f3e9

RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006

RBP: 00007efeffee2ee0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000009120 R11: 0000000000000246 R12: 00007efeffee2f70
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>


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