WARNING in handle_exception_nmi

Status: auto-obsoleted due to no activity on 2024/08/07 19:47
Reported-by: syzbot+d05e19e12dfb6dc0ec91@syzkaller.appspotmail.com
First crash: 1184d, last: 837d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2024/06/11 upstream (ToT) 83a7eefedc9b C Didn't crash
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in handle_exception_nmi origin:upstream missing-backport -1 syz, C error 25 816d 1173d 0/3 upstream: reported C repro on 2023/05/29 20:49
upstream WARNING in handle_exception_nmi (2) prio:high kvm-x86 -1 syz, C inconclusive inconclusive 334 4d12h 1634d 0/29 upstream: reported C repro on 2022/02/22 05:18
upstream WARNING in handle_exception_nmi kvm-x86 -1 syz, C error done 2653 2138d 2143d 15/29 fixed on 2020/11/16 12:12
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2024/06/01 05:59 14m bisect fix linux-5.15.y error job log
2024/04/29 17:47 1h59m bisect fix linux-5.15.y OK (0) job log log
2024/03/29 01:40 2h55m bisect fix linux-5.15.y OK (0) job log log
2024/02/27 21:14 1h40m bisect fix linux-5.15.y OK (0) job log log
2024/01/18 11:29 3h08m bisect fix linux-5.15.y OK (0) job log log
2023/12/18 04:30 1h47m bisect fix linux-5.15.y OK (0) job log log
2023/11/18 02:10 1h44m bisect fix linux-5.15.y OK (0) job log log
2023/10/17 14:42 59m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
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: 3500 at arch/x86/kvm/vmx/vmx.c:4876 handle_exception_nmi+0xc21/0xe80
Modules linked in:
CPU: 0 PID: 3500 Comm: syz-executor383 Not tainted 5.15.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:handle_exception_nmi+0xc21/0xe80 arch/x86/kvm/vmx/vmx.c:4876
Code: 1d a8 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 19 1e a8 00 e9 f4 f4 ff ff e8 1f b2 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:ffffc900011df490 EFLAGS: 00010293
RAX: ffffffff81214e81 RBX: 0000000000000000 RCX: ffff8880131bbb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000030000064 R08: ffffffff81214937 R09: ffffed100f05804d
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1100f05804c
R13: 1ffff1100f05801e R14: ffff8880782c0260 R15: ffff8880782c0000
FS:  0000555555b11300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000030000012 CR3: 0000000074f43000 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+0x3367/0x9850 arch/x86/kvm/x86.c:10034
 vcpu_run arch/x86/kvm/x86.c:10124 [inline]
 kvm_arch_vcpu_ioctl_run+0xa5e/0x1f80 arch/x86/kvm/x86.c:10361
 kvm_vcpu_ioctl+0x7f0/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3881
 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:0x7f9911e9b3e9
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:00007fffb6efe138 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9911e9b3e9
RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000006
RBP: 00007f9911e5eee0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000009120 R11: 0000000000000246 R12: 00007f9911e5ef70
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (21):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/07/04 12:08 linux-5.15.y 4af60700a60c 6e553898 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/23 14:33 linux-5.15.y f67653019430 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/17 04:03 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/17 03:14 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/17 02:39 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/17 02:14 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/17 01:51 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/05/19 01:50 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/14 07:57 linux-5.15.y aff03380bda4 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/11 07:50 linux-5.15.y aff03380bda4 6654cf89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/06 01:37 linux-5.15.y 8f790700c974 0b6286dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/03 23:45 linux-5.15.y 8f790700c974 696ea0d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/03 23:36 linux-5.15.y 8f790700c974 696ea0d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/09/03 23:24 linux-5.15.y 8f790700c974 696ea0d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/21 08:06 linux-5.15.y 471e639e59d1 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/16 07:05 linux-5.15.y 471e639e59d1 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/16 06:53 linux-5.15.y 471e639e59d1 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/09 03:53 linux-5.15.y d7af3e5ba454 058b3a5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/06/09 03:45 linux-5.15.y d7af3e5ba454 058b3a5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/05/29 20:59 linux-5.15.y 1fe619a7d252 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
2023/05/19 01:30 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in handle_exception_nmi
* Struck through repros no longer work on HEAD.