From: Sean Christopherson <seanjc@google.com>
To: Michal Luczaj <mhal@rbox.co>
Cc: Will Deacon <will@kernel.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Alexander Potapenko <glider@google.com>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] KVM: Fix error path in kvm_vm_ioctl_create_vcpu() on xa_store() failure
Date: Wed, 7 Aug 2024 14:58:35 -0700 [thread overview]
Message-ID: <ZrPuC59gatPJ4UzQ@google.com> (raw)
In-Reply-To: <b0c3552b-1efd-4c48-8d86-91ee16e7222a@rbox.co>
On Tue, Aug 06, 2024, Michal Luczaj wrote:
> On 8/6/24 00:56, Sean Christopherson wrote:
> > [...]
> > + /*
> > + * xa_store() should never fail, see xa_reserve() above. Leak the vCPU
> > + * if the impossible happens, as userspace already has access to the
> > + * vCPU, i.e. freeing the vCPU before userspace puts its file reference
> > + * would trigger a use-after-free.
> > + */
> > if (KVM_BUG_ON(xa_store(&kvm->vcpu_array, vcpu->vcpu_idx, vcpu, 0), kvm)) {
> > - r = -EINVAL;
> > - goto kvm_put_xa_release;
> > + mutex_unlock(&vcpu->mutex);
> > + return -EINVAL;
> > }
> >
> > /*
> > @@ -4302,6 +4310,7 @@ static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, unsigned long id)
> > */
> > smp_wmb();
> > atomic_inc(&kvm->online_vcpus);
> > + mutex_unlock(&vcpu->mutex);
> >
> > mutex_unlock(&kvm->lock);
> > kvm_arch_vcpu_postcreate(vcpu);
> > @@ -4309,6 +4318,7 @@ static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, unsigned long id)
> > return r;
> >
> > kvm_put_xa_release:
> > + mutex_unlock(&vcpu->mutex);
> > kvm_put_kvm_no_destroy(kvm);
> > xa_release(&kvm->vcpu_array, vcpu->vcpu_idx);
>
> Since we're handling the impossible, isn't the BUG_ON part missing
> mutex_unlock(&kvm->lock)?
Doh, yes.
prev parent reply other threads:[~2024-08-07 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 15:56 [PATCH] KVM: Fix error path in kvm_vm_ioctl_create_vcpu() on xa_store() failure Will Deacon
2024-07-30 18:55 ` Michal Luczaj
2024-07-30 23:31 ` Sean Christopherson
2024-07-31 13:31 ` Will Deacon
2024-07-31 15:49 ` Michal Luczaj
2024-07-31 16:18 ` Sean Christopherson
2024-07-31 19:27 ` Michal Luczaj
2024-08-01 12:41 ` Will Deacon
2024-08-04 21:05 ` Michal Luczaj
2024-08-05 22:56 ` Sean Christopherson
2024-08-05 23:02 ` Paolo Bonzini
2024-08-06 16:59 ` Michal Luczaj
2024-08-07 21:58 ` 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=ZrPuC59gatPJ4UzQ@google.com \
--to=seanjc@google.com \
--cc=glider@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mhal@rbox.co \
--cc=pbonzini@redhat.com \
--cc=will@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