KVM: nVMX: Fix consistency check on injected exception error code
authorSean Christopherson <sean.j.christopherson@intel.com>
Tue, 1 Oct 2019 16:21:23 +0000 (09:21 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Thu, 3 Oct 2019 10:32:44 +0000 (12:32 +0200)
commit567926cca99ba1750be8aae9c4178796bf9bb90b
tree09629b2fce3fdbb2b62a4071797a5b7df0e565a8
parentd53a4c8e77dae2b71cd9b3fd249ae538f137caeb
KVM: nVMX: Fix consistency check on injected exception error code

Current versions of Intel's SDM incorrectly state that "bits 31:15 of
the VM-Entry exception error-code field" must be zero.  In reality, bits
31:16 must be zero, i.e. error codes are 16-bit values.

The bogus error code check manifests as an unexpected VM-Entry failure
due to an invalid code field (error number 7) in L1, e.g. when injecting
a #GP with error_code=0x9f00.

Nadav previously reported the bug[*], both to KVM and Intel, and fixed
the associated kvm-unit-test.

[*] https://patchwork.kernel.org/patch/11124749/

Reported-by: Nadav Amit <namit@vmware.com>
Cc: stable@vger.kernel.org
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Reviewed-by: Jim Mattson <jmattson@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/vmx/nested.c