[v5.15] WARNING in handle_exception_nmi

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15801731280000
kernel config: https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link: https://syzkaller.appspot.com/bug?extid=d05e19e12dfb6dc0ec91
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/b65d6c2ec328/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf811ebac37b/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2f32fdecf97/bzImage-9d6bde85.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 15213 at arch/x86/kvm/vmx/vmx.c:4876 handle_exception_nmi+0xc21/0xe80
Modules linked in:
CPU: 1 PID: 15213 Comm: syz-executor.2 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:handle_exception_nmi+0xc21/0xe80 arch/x86/kvm/vmx/vmx.c:4876
Code: f8 a7 00 e9 43 f5 ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 01 f5 ff ff 48 89 ef e8 b9 f8 a7 00 e9 f4 f4 ff ff e8 cf 9c 5e 00 <0f> 0b e9 bc fa ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 13 f6 ff
RSP: 0018:ffffc9000317f490 EFLAGS: 00010283
RAX: ffffffff81214c11 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90003bd6000 RSI: 0000000000007ee8 RDI: 0000000000007ee9
RBP: 00000000009d23e2 R08: ffffffff812146c7 R09: ffffed100f0ca84d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100f0ca84c
R13: 1ffff1100f0ca81e R14: ffff888078654260 R15: ffff888078654000
FS: 00007f24848a4700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc5da4ea218 CR3: 00000000679b4000 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:6136 [inline]
vmx_handle_exit+0xb93/0x1820 arch/x86/kvm/vmx/vmx.c:6153
vcpu_enter_guest+0x33b8/0x9800 arch/x86/kvm/x86.c:10031
vcpu_run arch/x86/kvm/x86.c:10121 [inline]
kvm_arch_vcpu_ioctl_run+0xa5e/0x1f80 arch/x86/kvm/x86.c:10358
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3863
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:0x7f2486332169
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:00007f24848a4168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2486451f80 RCX: 00007f2486332169
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006
RBP: 00007f248638dca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd2ab7a25f R14: 00007f24848a4300 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: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=17e3e141280000

kernel config: https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link: https://syzkaller.appspot.com/bug?extid=d05e19e12dfb6dc0ec91
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=1456610e280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e97af9280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65d6c2ec328/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf811ebac37b/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2f32fdecf97/bzImage-9d6bde85.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d05e19...@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: 0 PID: 3497 at arch/x86/kvm/vmx/vmx.c:4876 handle_exception_nmi+0xc21/0xe80
Modules linked in:
CPU: 0 PID: 3497 Comm: syz-executor326 Not tainted 5.15.112-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:handle_exception_nmi+0xc21/0xe80 arch/x86/kvm/vmx/vmx.c:4876
Code: f8 a7 00 e9 43 f5 ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 01 f5 ff ff 48 89 ef e8 b9 f8 a7 00 e9 f4 f4 ff ff e8 cf 9c 5e 00 <0f> 0b e9 bc fa ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 13 f6 ff

RSP: 0018:ffffc90002d9f490 EFLAGS: 00010293
RAX: ffffffff81214c11 RBX: 0000000000000000 RCX: ffff888079e68000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000009d23e2 R08: ffffffff812146c7 R09: ffffed100f29004d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100f29004c
R13: 1ffff1100f29001e R14: ffff888079480260 R15: ffff888079480000
FS: 0000555555f67300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

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

CR2: ffffffffaa101fe4 CR3: 000000007b37c000 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:6136 [inline]
vmx_handle_exit+0xb93/0x1820 arch/x86/kvm/vmx/vmx.c:6153
vcpu_enter_guest+0x33b8/0x9800 arch/x86/kvm/x86.c:10031
vcpu_run arch/x86/kvm/x86.c:10121 [inline]
kvm_arch_vcpu_ioctl_run+0xa5e/0x1f80 arch/x86/kvm/x86.c:10358
kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3863
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:0x7f74dab813f9
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:00007fffdb6af448 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f74dab813f9

RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006

RBP: 00007f74dab44ef0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000009120 R11: 0000000000000246 R12: 00007f74dab44f80
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.