mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Ido Yariv" <ido@wizery.com>, "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: fix wbinvd_dirty_mask use-after-free
Date: Mon, 24 Oct 2016 16:15:51 +0200	[thread overview]
Message-ID: <5488ed61-ac8b-c067-3508-d6832367e4ea@redhat.com> (raw)
In-Reply-To: <1477067997-17845-1-git-send-email-ido@wizery.com>



On 21/10/2016 18:39, Ido Yariv wrote:
> vcpu->arch.wbinvd_dirty_mask may still be used after freeing it,
> corrupting memory. For example, the following call trace may set a bit
> in an already freed cpu mask:
>     kvm_arch_vcpu_load
>     vcpu_load
>     vmx_free_vcpu_nested
>     vmx_free_vcpu
>     kvm_arch_vcpu_free
> 
> Fix this by deferring freeing of wbinvd_dirty_mask.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Ido Yariv <ido@wizery.com>
> ---
>  arch/x86/kvm/x86.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 6c633de..9ec8c1d 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -7410,10 +7410,12 @@ void kvm_put_guest_fpu(struct kvm_vcpu *vcpu)
>  
>  void kvm_arch_vcpu_free(struct kvm_vcpu *vcpu)
>  {
> +	void *wbinvd_dirty_mask = vcpu->arch.wbinvd_dirty_mask;
> +
>  	kvmclock_reset(vcpu);
>  
> -	free_cpumask_var(vcpu->arch.wbinvd_dirty_mask);
>  	kvm_x86_ops->vcpu_free(vcpu);
> +	free_cpumask_var(wbinvd_dirty_mask);
>  }
>  
>  struct kvm_vcpu *kvm_arch_vcpu_create(struct kvm *kvm,
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

  reply	other threads:[~2016-10-24 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 16:39 Ido Yariv
2016-10-24 14:15 ` Paolo Bonzini [this message]
2016-10-24 15:23 ` Radim Krčmář

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=5488ed61-ac8b-c067-3508-d6832367e4ea@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hpa@zytor.com \
    --cc=ido@wizery.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®