From: Paolo Bonzini <pbonzini@redhat.com>
To: "David Rientjes" <rientjes@google.com>,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Joerg Roedel" <joro@8bytes.org>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: Borislav Petkov <bp@suse.de>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] KVM: SVM: prevent DBG_DECRYPT and DBG_ENCRYPT overflow
Date: Fri, 5 Apr 2019 20:50:13 +0200 [thread overview]
Message-ID: <7b33b8fb-fa6b-5fbb-8166-218aef5216f2@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1903251146160.188887@chino.kir.corp.google.com>
On 25/03/19 19:47, David Rientjes wrote:
> This ensures that the address and length provided to DBG_DECRYPT and
> DBG_ENCRYPT do not cause an overflow.
>
> At the same time, pass the actual number of pages pinned in memory to
> sev_unpin_memory() as a cleanup.
>
> Reported-by: Cfir Cohen <cfir@google.com>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> arch/x86/kvm/svm.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -6799,7 +6799,8 @@ static int sev_dbg_crypt(struct kvm *kvm, struct kvm_sev_cmd *argp, bool dec)
> struct page **src_p, **dst_p;
> struct kvm_sev_dbg debug;
> unsigned long n;
> - int ret, size;
> + unsigned int size;
> + int ret;
>
> if (!sev_guest(kvm))
> return -ENOTTY;
> @@ -6807,6 +6808,11 @@ static int sev_dbg_crypt(struct kvm *kvm, struct kvm_sev_cmd *argp, bool dec)
> if (copy_from_user(&debug, (void __user *)(uintptr_t)argp->data, sizeof(debug)))
> return -EFAULT;
>
> + if (!debug.len || debug.src_uaddr + debug.len < debug.src_uaddr)
> + return -EINVAL;
> + if (!debug.dst_uaddr)
> + return -EINVAL;
> +
> vaddr = debug.src_uaddr;
> size = debug.len;
> vaddr_end = vaddr + size;
> @@ -6857,8 +6863,8 @@ static int sev_dbg_crypt(struct kvm *kvm, struct kvm_sev_cmd *argp, bool dec)
> dst_vaddr,
> len, &argp->error);
>
> - sev_unpin_memory(kvm, src_p, 1);
> - sev_unpin_memory(kvm, dst_p, 1);
> + sev_unpin_memory(kvm, src_p, n);
> + sev_unpin_memory(kvm, dst_p, n);
>
> if (ret)
> goto err;
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-04-05 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 18:47 David Rientjes
2019-03-28 13:58 ` Singh, Brijesh
2019-04-04 20:55 ` David Rientjes
2019-04-05 18:50 ` Paolo Bonzini [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=7b33b8fb-fa6b-5fbb-8166-218aef5216f2@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.com \
--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®