From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.160.70 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795132002; b=oPBba1Fnb/X5CByYoWFH4byA6y6Qcq+xqxwoaZKPfm0cxHrvoPFQX/si17igF79WfQOV B0hxGM914OrCey/PA67E/fgH358UINW77j3NO4DWU0ZpTDmQd4zLQP5B4BErDBZMLW+rw LgshCCS8QtN05nlcBLW3xhsWS9ZvN/5k/4kWvMB96fmclKy2FDjptyEcl8d5TlLC0eq8g vLyiMABvrFdKx9xqkWUT7T8PD2rZPXUC7xW9t4rDMuR6q/SrP9XbvssIIsj9yepPuTi4x +AXE/tYu0LN8pDWvuHkwV4xYmv9uu4AOY1Nv6pizwUEFDyMfzxlfQmqObVS+GtpsuiA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795132002; h=DMARC-Filter:Received:X-Google-DKIM-Signature:X-Forwarded-Encrypted: X-Gm-Message-State:MIME-Version:X-Received:Date:In-Reply-To: X-Google-Appengine-App-Id:X-Google-Appengine-App-Id-Alias:Message-ID: Subject:From:To:Cc:Content-Type; bh=rQB34CXlJwcWdBt45rejxcfsByac8tggb9Dt3exb3D8=; b=FyukuafbzYPhYMk+QfRgMHLrkf4ZmqmPoDRWnHxWi+x7xYd3iOk0HvU10DAWOE3X6uSX KuH5ex33iobB/kMp62yY8tI7ojtgbUItbcOc7tuEDT6XZdL0RjNMVjrNNw0xuamnv/+n8 g9bcmu1fcCbTVQDVPtpmur1cCDNuXpelNESSWiGqvC5tG/bF/SPT8SffVSK0GitaNSNV9 nFGD1jXC8KaHUXnzYSDIf7n+dk9XpGil3+n3crA35XOKyUCLtBTx58ze4arqzza4Z/x5D gS+JGHDfU4/MF2j9OjrExZmleZKH/It469JApNfSelYQVTpX9E5uD4q/pLSL2jtKsPg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=fail header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.remote-ip=209.85.160.70 Received: from mail-oa1-f70.google.com (mail-oa1-f70.google.com [209.85.160.70]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3F785606A338 for ; Thu, 19 Nov 2026 23:46:41 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 3F785606A338 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oa1-f70.google.com with SMTP id 586e51a60fabf-469debb526fso401961fac.0 for ; Thu, 19 Nov 2026 15:46:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1795132001; x=1795736801; h=content-type:cc:to:from:subject:message-id:in-reply-to:date :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to:content-type; bh=rQB34CXlJwcWdBt45rejxcfsByac8tggb9Dt3exb3D8=; b=ZwquF2iTbSJE0XWcQoVZUK8e0eCjf8iF50Sd/q3aPiMNIi3c41ETNdjTqmM010cuHq 1MsHLpwgPXzyTI9cKbDokpsFEmugB0rtBSJe00cRulCAmaeAEvoyGWz5f2jk6P6fZ7+B /P+fKYZBva0qzGCDlKIvhtq9gyizI8MFANcWt5/itouWCBSPBD49/7x9IxSMQlCNxLEO wlXYSs9J655+0okJk0AlEynsuP5hLS+0YrZdS9RrgE3LNvsRT8GDmD69yygg2auNrJyu 5IZ16HGOqQskst3wfjMqgfMo8c69XKDTD0jQb2ezzJ2ymdhPGYnF1Ce3xPYzt3enfLhw W4Qg== X-Forwarded-Encrypted: i=1; AL+hErENoQy5y2oeR/50Mn1Vi/aI68j6Bmh+qlZSoP97OWjmGf8+sTlQJoTdVPrR0msJa3W7+6fNCNqvsn9Y7t0=@vger.kernel.org X-Gm-Message-State: APuU4Z8TeEh8Fclap4Jgq5tngrp6IrJ6xXz2nopfErDiyMUrkk2PK1c0 vjOGmGM9G/85a8TslNWFLowYingEMJ09qey8bYSjJLk82cC04Fg8B0E5VHhYqMipmkcSGio3QpP O+IVIIlQCkO0H+6kYwHGLMt5w17t612stbLMewfutadNnQtN5fWBEPlvNUgo= X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Received: by 2002:a05:6809:18:10b0:57a:5851:f586 with SMTP id 5614622812f47-57a5851f5b7mr578539b6e.49.1795132001018; Thu, 19 Nov 2026 15:46:41 -0800 (PST) Date: Thu, 19 Nov 2026 15:46:40 -0800 In-Reply-To: X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6aff8a60.6ea51c61.12eec.0000.GAE@google.com> Subject: Re: [syzbot] [kvm-x86?] WARNING in __nested_vmx_vmexit From: syzbot To: seanjc@google.com Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, pbonzini@redhat.com, seanjc@google.com, syzkaller-bugs@googlegroups.com, tglx@kernel.org, x86@kernel.org Content-Type: text/plain; charset="UTF-8" > 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: >> >> 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 >> > > 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.