All of lore.kernel.org
 help / color / mirror / Atom feed
* [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit
@ 2026-11-19 22:07 syzbot
  2026-11-19 23:46 ` Sean Christopherson
  0 siblings, 1 reply; 3+ messages in thread
From: syzbot @ 2026-11-19 22:07 UTC (permalink / raw)
  To: bp, dave.hansen, hpa, kvm, linux-kernel, mingo, pbonzini, seanjc,
	syzkaller-bugs, tglx, x86

Hello,

syzbot found the following issue on:

HEAD commit:    7475ea8b5861 Linux 7.4-rc2
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12372a4e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
dashboard link: https://syzkaller.appspot.com/bug?extid=483ee9b97423483ca602
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1360d4d9580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17839409580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-7475ea8b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/db4e8a9a4461/vmlinux-7475ea8b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2abcfcabee20/bzImage-7475ea8b.xz

AI-generated root cause summary:
When an L1 vCPU encounters a hardware VM-Fail on VM-Entry, `vmx_handle_exit()`
processes the failure and returns KVM_EXIT_FAIL_ENTRY to userspace without
clearing the `vmx->fail` flag. If userspace then calls KVM_SET_NESTED_STATE with
KVM_STATE_NESTED_GUEST_MODE set, the vCPU enters guest mode without resetting
`vmx->fail`. If the VM is subsequently torn down without another KVM_RUN,
`vmx_leave_nested()` synthesizes a nested VM-exit where `__nested_vmx_vmexit()`
observes the stale `vmx->fail == 1` and reads VM_INSTRUCTION_ERROR from vmcs02
(which was never launched), triggering a WARN_ON_ONCE because
VM_INSTRUCTION_ERROR is not VMXERR_ENTRY_INVALID_CONTROL_FIELD.

full analysis:  https://syzkaller.appspot.com/x/ai_root_cause?x=483ee9b97423483ca602

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

kvm_intel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
------------[ cut here ]------------
vmcs_read32(VM_INSTRUCTION_ERROR) != VMXERR_ENTRY_INVALID_CONTROL_FIELD
WARNING: arch/x86/kvm/vmx/nested.c:5149 at __nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149, CPU#1: syz.0.17/6007
Modules linked in:
CPU: 1 UID: 0 PID: 6007 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149
Code: ff ff e8 0f a0 67 00 90 bf 0e 44 00 00 e8 c4 ed f8 ff 90 31 db e9 01 ec ff ff e8 f7 9f 67 00 e8 f2 1b 48 0a e8 ed 9f 67 00 90 <0f> 0b 90 e9 6a ff ff ff e8 df 9f 67 00 90 bf 00 44 00 00 e8 94 ed
RSP: 0018:ffffc9000338f960 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88802c514b00 RSI: ffffffff81a6e113 RDI: 0000000000000005
RBP: ffffc9000338fac0 R08: 0000000000000007 R09: 0000000000000000
R10: ffff888035f7003f R11: 0000000000000000 R12: 0000000000000001
R13: ffff8880382442ec R14: 0000000000000000 R15: ffff888035f70000
FS:  00005555645d0500(0000) GS:ffff8880d4571000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b5cc929ff0 CR3: 000000003db67000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 nested_vmx_vmexit arch/x86/kvm/vmx/nested.h:46 [inline]
 vmx_leave_nested arch/x86/kvm/vmx/nested.c:6895 [inline]
 nested_vmx_free_vcpu+0xb3/0xd0 arch/x86/kvm/vmx/nested.c:389
 vmx_vcpu_free+0x94/0x340 arch/x86/kvm/vmx/vmx.c:7519
 kvm_arch_vcpu_destroy+0x159/0x3e0 arch/x86/kvm/x86.c:9558
 kvm_vcpu_destroy virt/kvm/kvm_main.c:477 [inline]
 kvm_destroy_vcpus+0x24e/0x3c0 virt/kvm/kvm_main.c:497
 kvm_arch_destroy_vm+0xc7/0x230 arch/x86/kvm/x86.c:10129
 kvm_destroy_vm virt/kvm/kvm_main.c:1313 [inline]
 kvm_put_kvm+0x556/0xc00 virt/kvm/kvm_main.c:1350
 kvm_vm_release+0x65/0x80 virt/kvm/kvm_main.c:1375
 __fput+0x3fb/0xb50 fs/file_table.c:512
 fput_close_sync+0x118/0x250 fs/file_table.c:618
 filp_close_sync+0x75/0xa0 fs/open.c:1574
 __range_close+0x4a6/0x8b0 fs/file.c:919
 __do_sys_close_range fs/file.c:1003 [inline]
 __se_sys_close_range fs/file.c:954 [inline]
 __x64_sys_close_range+0x1f8/0x430 fs/file.c:954
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5f6ab9fb19
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff0931e598 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: ffffffffffffffda RBX: 00007fff0931e680 RCX: 00007f5f6ab9fb19
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 000000000000e232 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b2fb20000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5f6ae25fac R14: 00007f5f6ae25fa8 R15: 00007f5f6ae25fa0
 </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@googlegroups.com.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit
  2026-11-19 22:07 [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit syzbot
@ 2026-11-19 23:46 ` Sean Christopherson
  2026-11-19 23:46   ` syzbot
  0 siblings, 1 reply; 3+ messages in thread
From: Sean Christopherson @ 2026-11-19 23:46 UTC (permalink / raw)
  To: syzbot
  Cc: bp, dave.hansen, hpa, kvm, linux-kernel, mingo, pbonzini,
	syzkaller-bugs, tglx, x86

On Thu, Nov 19, 2026, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    7475ea8b5861 Linux 7.4-rc2
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12372a4e580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
> dashboard link: https://syzkaller.appspot.com/bug?extid=483ee9b97423483ca602
> compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1360d4d9580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17839409580000
> 
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-7475ea8b.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/db4e8a9a4461/vmlinux-7475ea8b.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/2abcfcabee20/bzImage-7475ea8b.xz
> 
> AI-generated root cause summary:
> When an L1 vCPU encounters a hardware VM-Fail on VM-Entry, `vmx_handle_exit()`
> processes the failure and returns KVM_EXIT_FAIL_ENTRY to userspace without
> clearing the `vmx->fail` flag. If userspace then calls KVM_SET_NESTED_STATE with
> KVM_STATE_NESTED_GUEST_MODE set, the vCPU enters guest mode without resetting
> `vmx->fail`. If the VM is subsequently torn down without another KVM_RUN,
> `vmx_leave_nested()` synthesizes a nested VM-exit where `__nested_vmx_vmexit()`
> observes the stale `vmx->fail == 1` and reads VM_INSTRUCTION_ERROR from vmcs02
> (which was never launched), triggering a WARN_ON_ONCE because
> VM_INSTRUCTION_ERROR is not VMXERR_ENTRY_INVALID_CONTROL_FIELD.
> 
> full analysis:  https://syzkaller.appspot.com/x/ai_root_cause?x=483ee9b97423483ca602
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+483ee9b97423483ca602@syzkaller.appspotmail.com
> 
> kvm_intel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
> ------------[ cut here ]------------
> vmcs_read32(VM_INSTRUCTION_ERROR) != VMXERR_ENTRY_INVALID_CONTROL_FIELD
> WARNING: arch/x86/kvm/vmx/nested.c:5149 at __nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149, CPU#1: syz.0.17/6007
> Modules linked in:
> CPU: 1 UID: 0 PID: 6007 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> RIP: 0010:__nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149
> Code: ff ff e8 0f a0 67 00 90 bf 0e 44 00 00 e8 c4 ed f8 ff 90 31 db e9 01 ec ff ff e8 f7 9f 67 00 e8 f2 1b 48 0a e8 ed 9f 67 00 90 <0f> 0b 90 e9 6a ff ff ff e8 df 9f 67 00 90 bf 00 44 00 00 e8 94 ed
> RSP: 0018:ffffc9000338f960 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: ffff88802c514b00 RSI: ffffffff81a6e113 RDI: 0000000000000005
> RBP: ffffc9000338fac0 R08: 0000000000000007 R09: 0000000000000000
> R10: ffff888035f7003f R11: 0000000000000000 R12: 0000000000000001
> R13: ffff8880382442ec R14: 0000000000000000 R15: ffff888035f70000
> FS:  00005555645d0500(0000) GS:ffff8880d4571000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000055b5cc929ff0 CR3: 000000003db67000 CR4: 0000000000352ef0
> Call Trace:
>  <TASK>
>  nested_vmx_vmexit arch/x86/kvm/vmx/nested.h:46 [inline]
>  vmx_leave_nested arch/x86/kvm/vmx/nested.c:6895 [inline]
>  nested_vmx_free_vcpu+0xb3/0xd0 arch/x86/kvm/vmx/nested.c:389
>  vmx_vcpu_free+0x94/0x340 arch/x86/kvm/vmx/vmx.c:7519
>  kvm_arch_vcpu_destroy+0x159/0x3e0 arch/x86/kvm/x86.c:9558
>  kvm_vcpu_destroy virt/kvm/kvm_main.c:477 [inline]
>  kvm_destroy_vcpus+0x24e/0x3c0 virt/kvm/kvm_main.c:497
>  kvm_arch_destroy_vm+0xc7/0x230 arch/x86/kvm/x86.c:10129
>  kvm_destroy_vm virt/kvm/kvm_main.c:1313 [inline]
>  kvm_put_kvm+0x556/0xc00 virt/kvm/kvm_main.c:1350
>  kvm_vm_release+0x65/0x80 virt/kvm/kvm_main.c:1375
>  __fput+0x3fb/0xb50 fs/file_table.c:512
>  fput_close_sync+0x118/0x250 fs/file_table.c:618
>  filp_close_sync+0x75/0xa0 fs/open.c:1574
>  __range_close+0x4a6/0x8b0 fs/file.c:919
>  __do_sys_close_range fs/file.c:1003 [inline]
>  __se_sys_close_range fs/file.c:954 [inline]
>  __x64_sys_close_range+0x1f8/0x430 fs/file.c:954
>  do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
>  do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f5f6ab9fb19
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007fff0931e598 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
> RAX: ffffffffffffffda RBX: 00007fff0931e680 RCX: 00007f5f6ab9fb19
> RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
> RBP: 000000000000e232 R08: 0000000000000001 R09: 0000000000000000
> R10: 0000001b2fb20000 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007f5f6ae25fac R14: 00007f5f6ae25fa8 R15: 00007f5f6ae25fa0
>  </TASK>

Oh, _now_ you find it on an upstream kernel? :-D  This presumably the same thing
that was fixed by:

#syz test https://github.com/kvm-x86/linux.git 40c0e9dd6b6dfbdbbdbf5d7936d2819b2d84d25c

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit
  2026-11-19 23:46 ` Sean Christopherson
@ 2026-11-19 23:46   ` syzbot
  0 siblings, 0 replies; 3+ messages in thread
From: syzbot @ 2026-11-19 23:46 UTC (permalink / raw)
  To: seanjc
  Cc: bp, dave.hansen, hpa, kvm, linux-kernel, mingo, pbonzini, seanjc,
	syzkaller-bugs, tglx, x86

> On Thu, Nov 19, 2026, syzbot wrote:
>> Hello,
>> 
>> syzbot found the following issue on:
>> 
>> HEAD commit:    7475ea8b5861 Linux 7.4-rc2
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12372a4e580000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf189394a856f11
>> dashboard link: https://syzkaller.appspot.com/bug?extid=483ee9b97423483ca602
>> compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1360d4d9580000
>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17839409580000
>> 
>> Downloadable assets:
>> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-7475ea8b.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/db4e8a9a4461/vmlinux-7475ea8b.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/2abcfcabee20/bzImage-7475ea8b.xz
>> 
>> AI-generated root cause summary:
>> When an L1 vCPU encounters a hardware VM-Fail on VM-Entry, `vmx_handle_exit()`
>> processes the failure and returns KVM_EXIT_FAIL_ENTRY to userspace without
>> clearing the `vmx->fail` flag. If userspace then calls KVM_SET_NESTED_STATE with
>> KVM_STATE_NESTED_GUEST_MODE set, the vCPU enters guest mode without resetting
>> `vmx->fail`. If the VM is subsequently torn down without another KVM_RUN,
>> `vmx_leave_nested()` synthesizes a nested VM-exit where `__nested_vmx_vmexit()`
>> observes the stale `vmx->fail == 1` and reads VM_INSTRUCTION_ERROR from vmcs02
>> (which was never launched), triggering a WARN_ON_ONCE because
>> VM_INSTRUCTION_ERROR is not VMXERR_ENTRY_INVALID_CONTROL_FIELD.
>> 
>> full analysis:  https://syzkaller.appspot.com/x/ai_root_cause?x=483ee9b97423483ca602
>> 
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+483ee9b97423483ca602@syzkaller.appspotmail.com
>> 
>> kvm_intel: set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
>> ------------[ cut here ]------------
>> vmcs_read32(VM_INSTRUCTION_ERROR) != VMXERR_ENTRY_INVALID_CONTROL_FIELD
>> WARNING: arch/x86/kvm/vmx/nested.c:5149 at __nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149, CPU#1: syz.0.17/6007
>> Modules linked in:
>> CPU: 1 UID: 0 PID: 6007 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
>> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
>> RIP: 0010:__nested_vmx_vmexit+0x2734/0x4000 arch/x86/kvm/vmx/nested.c:5149
>> Code: ff ff e8 0f a0 67 00 90 bf 0e 44 00 00 e8 c4 ed f8 ff 90 31 db e9 01 ec ff ff e8 f7 9f 67 00 e8 f2 1b 48 0a e8 ed 9f 67 00 90 <0f> 0b 90 e9 6a ff ff ff e8 df 9f 67 00 90 bf 00 44 00 00 e8 94 ed
>> RSP: 0018:ffffc9000338f960 EFLAGS: 00010293
>> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
>> RDX: ffff88802c514b00 RSI: ffffffff81a6e113 RDI: 0000000000000005
>> RBP: ffffc9000338fac0 R08: 0000000000000007 R09: 0000000000000000
>> R10: ffff888035f7003f R11: 0000000000000000 R12: 0000000000000001
>> R13: ffff8880382442ec R14: 0000000000000000 R15: ffff888035f70000
>> FS:  00005555645d0500(0000) GS:ffff8880d4571000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 000055b5cc929ff0 CR3: 000000003db67000 CR4: 0000000000352ef0
>> Call Trace:
>>  <TASK>
>>  nested_vmx_vmexit arch/x86/kvm/vmx/nested.h:46 [inline]
>>  vmx_leave_nested arch/x86/kvm/vmx/nested.c:6895 [inline]
>>  nested_vmx_free_vcpu+0xb3/0xd0 arch/x86/kvm/vmx/nested.c:389
>>  vmx_vcpu_free+0x94/0x340 arch/x86/kvm/vmx/vmx.c:7519
>>  kvm_arch_vcpu_destroy+0x159/0x3e0 arch/x86/kvm/x86.c:9558
>>  kvm_vcpu_destroy virt/kvm/kvm_main.c:477 [inline]
>>  kvm_destroy_vcpus+0x24e/0x3c0 virt/kvm/kvm_main.c:497
>>  kvm_arch_destroy_vm+0xc7/0x230 arch/x86/kvm/x86.c:10129
>>  kvm_destroy_vm virt/kvm/kvm_main.c:1313 [inline]
>>  kvm_put_kvm+0x556/0xc00 virt/kvm/kvm_main.c:1350
>>  kvm_vm_release+0x65/0x80 virt/kvm/kvm_main.c:1375
>>  __fput+0x3fb/0xb50 fs/file_table.c:512
>>  fput_close_sync+0x118/0x250 fs/file_table.c:618
>>  filp_close_sync+0x75/0xa0 fs/open.c:1574
>>  __range_close+0x4a6/0x8b0 fs/file.c:919
>>  __do_sys_close_range fs/file.c:1003 [inline]
>>  __se_sys_close_range fs/file.c:954 [inline]
>>  __x64_sys_close_range+0x1f8/0x430 fs/file.c:954
>>  do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
>>  do_syscall_64+0x123/0x7b0 arch/x86/entry/syscall_64.c:89
>>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
>> RIP: 0033:0x7f5f6ab9fb19
>> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48
>> RSP: 002b:00007fff0931e598 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
>> RAX: ffffffffffffffda RBX: 00007fff0931e680 RCX: 00007f5f6ab9fb19
>> RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
>> RBP: 000000000000e232 R08: 0000000000000001 R09: 0000000000000000
>> R10: 0000001b2fb20000 R11: 0000000000000246 R12: 0000000000000000
>> R13: 00007f5f6ae25fac R14: 00007f5f6ae25fa8 R15: 00007f5f6ae25fa0
>>  </TASK>
>
> Oh, _now_ you find it on an upstream kernel? :-D  This presumably the same thing
> that was fixed by:
>
> #syz test https://github.com/kvm-x86/linux.git 40c0e9dd6b6dfbdbbdbf5d7936d2819b2d84d25c

Patch testing via #syz test is temporarily disabled.
See https://github.com/google/syzkaller/issues/8122 for details.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-11-19 23:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-19 22:07 [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit syzbot
2026-11-19 23:46 ` Sean Christopherson
2026-11-19 23:46   ` syzbot

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.