From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Manuel Andreas <manuel.andreas@tum.de>
Subject: [PATCH v2 2/2] KVM: nVMX: Do eVMCS consistency check on VMFUNC controls iff they're enable
Date: Thu, 5 Nov 2026 11:07:33 -0800 [thread overview]
Message-ID: <20261105190733.3741959-3-seanjc@google.com> (raw)
In-Reply-To: <20261105190733.3741959-1-seanjc@google.com>
Check that the VM-function controls are actually enabled before performing
eVMCS-specific consistency checks, as the VMFUNC controls are supposed to
be completely ignored if they're not enabled. Per the SDM:
If the "enable VM functions" processor-based VM-execution control is 0,
no checks are performed on the VM-function controls.
Fixes: 3ff8a13d41b2 ("KVM: nVMX: WARN once and fail VM-Enter if eVMCS sees VMFUNC[63:32] != 0")
Fixes: a83502314ce3 ("x86/kvm/hyper-v: don't allow to turn on unsupported VMX controls for nested guests")
Cc: stable@vger.kernel.org
Reported-by: Manuel Andreas <manuel.andreas@tum.de>
Closes: https://lore.kernel.org/all/f1f39118-2e1b-476b-9a84-ef7d56412bdc@tum.de
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
arch/x86/kvm/vmx/hyperv.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kvm/vmx/hyperv.c b/arch/x86/kvm/vmx/hyperv.c
index 2b40ac32ff06..a1daf8f2ec5a 100644
--- a/arch/x86/kvm/vmx/hyperv.c
+++ b/arch/x86/kvm/vmx/hyperv.c
@@ -187,11 +187,10 @@ int nested_evmcs_check_controls(struct vmcs12 *vmcs12)
* controls in bits 63:32, i.e. dropping those bits on the consistency
* check is intentional.
*/
- if (WARN_ON_ONCE(vmcs12->vm_function_control >> 32))
- return -EINVAL;
-
- if (CC(!nested_evmcs_is_valid_controls(EVMCS_VMFUNC,
- vmcs12->vm_function_control)))
+ if (nested_cpu_has_vmfunc(vmcs12) &&
+ (WARN_ON_ONCE(vmcs12->vm_function_control >> 32) ||
+ CC(!nested_evmcs_is_valid_controls(EVMCS_VMFUNC,
+ vmcs12->vm_function_control))))
return -EINVAL;
return 0;
--
2.56.0.567.gdb80ae8cd5-goog
prev parent reply other threads:[~2026-11-05 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 19:07 [PATCH v2 0/2] KVM: nVMX: eVMCS consistency check fixes Sean Christopherson
2026-11-05 19:07 ` [PATCH v2 1/2] KVM: nVMX: Do eVMCS consistency check on secondary controls iff they're enable Sean Christopherson
2026-11-05 19:07 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261105190733.3741959-3-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.andreas@tum.de \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®