kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: Liran Alon <liran.alon@oracle.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field
Date: Thu, 05 Dec 2019 12:28:48 +0100	[thread overview]
Message-ID: <87o8wnroy7.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20191204214027.85958-1-jmattson@google.com>

Jim Mattson <jmattson@google.com> writes:

> According to the SDM, a VMWRITE in VMX non-root operation with an
> invalid VMCS-link pointer results in VMfailInvalid before the validity
> of the VMCS field in the secondary source operand is checked.
>
> Fixes: 6d894f498f5d1 ("KVM: nVMX: vmread/vmwrite: Use shadow vmcs12 if running L2")
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Cc: Liran Alon <liran.alon@oracle.com>
> ---
>  arch/x86/kvm/vmx/nested.c | 38 +++++++++++++++++++-------------------
>  1 file changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index 4aea7d304beb..146e1b40c69f 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -4864,6 +4864,25 @@ static int handle_vmwrite(struct kvm_vcpu *vcpu)
>  	if (vmx->nested.current_vmptr == -1ull)
>  		return nested_vmx_failInvalid(vcpu);
>  
> +	if (!is_guest_mode(vcpu)) {
> +		vmcs12 = get_vmcs12(vcpu);
> +
> +		/*
> +		 * Ensure vmcs12 is up-to-date before any VMWRITE that dirties
> +		 * vmcs12, else we may crush a field or consume a stale value.
> +		 */
> +		if (!is_shadow_field_rw(field))
> +			copy_vmcs02_to_vmcs12_rare(vcpu, vmcs12);

But (unless I'm missing some pre-requisite patch) we haven't set 'field'
yet, it happens later when we do

field = kvm_register_readl(vcpu, (((vmx_instruction_info) >> 28) & 0xf));

> +	} else {
> +		/*
> +		 * When vmcs->vmcs_link_pointer is -1ull, any VMWRITE
> +		 * to shadowed-field sets the ALU flags for VMfailInvalid.
> +		 */
> +		if (get_vmcs12(vcpu)->vmcs_link_pointer == -1ull)
> +			return nested_vmx_failInvalid(vcpu);
> +		vmcs12 = get_shadow_vmcs12(vcpu);
> +	}
> +
>  	if (vmx_instruction_info & (1u << 10))
>  		field_value = kvm_register_readl(vcpu,
>  			(((vmx_instruction_info) >> 3) & 0xf));
> @@ -4889,25 +4908,6 @@ static int handle_vmwrite(struct kvm_vcpu *vcpu)
>  		return nested_vmx_failValid(vcpu,
>  			VMXERR_VMWRITE_READ_ONLY_VMCS_COMPONENT);
>  
> -	if (!is_guest_mode(vcpu)) {
> -		vmcs12 = get_vmcs12(vcpu);
> -
> -		/*
> -		 * Ensure vmcs12 is up-to-date before any VMWRITE that dirties
> -		 * vmcs12, else we may crush a field or consume a stale value.
> -		 */
> -		if (!is_shadow_field_rw(field))
> -			copy_vmcs02_to_vmcs12_rare(vcpu, vmcs12);
> -	} else {
> -		/*
> -		 * When vmcs->vmcs_link_pointer is -1ull, any VMWRITE
> -		 * to shadowed-field sets the ALU flags for VMfailInvalid.
> -		 */
> -		if (get_vmcs12(vcpu)->vmcs_link_pointer == -1ull)
> -			return nested_vmx_failInvalid(vcpu);
> -		vmcs12 = get_shadow_vmcs12(vcpu);
> -	}
> -
>  	offset = vmcs_field_to_offset(field);
>  	if (offset < 0)
>  		return nested_vmx_failValid(vcpu,

-- 
Vitaly


  reply	other threads:[~2019-12-05 11:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 21:40 [PATCH] kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field Jim Mattson
2019-12-05 11:28 ` Vitaly Kuznetsov [this message]
2019-12-05 11:45 ` Paolo Bonzini
2019-12-05 13:11   ` Jim Mattson
2019-12-05 21:30     ` Jim Mattson
2019-12-05 21:54       ` Liran Alon
2019-12-05 22:11         ` Jim Mattson
2019-12-09 15:28         ` Nadav Amit
2019-12-09 22:58           ` Liran Alon
2019-12-10 22:22             ` Nadav Amit
2019-12-09 16:12       ` Paolo Bonzini
2019-12-09 23:34         ` Jim Mattson
2019-12-10  8:39           ` Paolo Bonzini

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=87o8wnroy7.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=liran.alon@oracle.com \
    --cc=pbonzini@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;
as well as URLs for NNTP newsgroup(s).