mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID (CVE-2019-19332)
Date: Wed, 18 Dec 2019 13:24:00 +0100	[thread overview]
Message-ID: <20191218122400.GD24886@zn.tnic> (raw)
In-Reply-To: <1575458412-10241-1-git-send-email-pbonzini@redhat.com>

On Wed, Dec 04, 2019 at 12:20:12PM +0100, Paolo Bonzini wrote:
> The bounds check was present in KVM_GET_SUPPORTED_CPUID but not
> KVM_GET_EMULATED_CPUID.
> 
> Reported-by: syzbot+e3f4897236c4eeb8af4f@syzkaller.appspotmail.com
> Fixes: 84cffe499b94 ("kvm: Emulate MOVBE", 2013-10-29)
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  arch/x86/kvm/cpuid.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> index 813a4d2e5c0c..cfafa320a8cf 100644
> --- a/arch/x86/kvm/cpuid.c
> +++ b/arch/x86/kvm/cpuid.c
> @@ -504,7 +504,7 @@ static inline int __do_cpuid_func(struct kvm_cpuid_entry2 *entry, u32 function,
>  
>  	r = -E2BIG;
>  
> -	if (*nent >= maxnent)
> +	if (WARN_ON(*nent >= maxnent))
>  		goto out;
>  
>  	do_host_cpuid(entry, function, 0);
> @@ -815,6 +815,9 @@ static inline int __do_cpuid_func(struct kvm_cpuid_entry2 *entry, u32 function,
>  static int do_cpuid_func(struct kvm_cpuid_entry2 *entry, u32 func,
>  			 int *nent, int maxnent, unsigned int type)
>  {
> +	if (*nent >= maxnent)
> +		return -E2BIG;
> +
>  	if (type == KVM_GET_EMULATED_CPUID)
>  		return __do_cpuid_func_emulated(entry, func, nent, maxnent);
>  
> -- 

Whoops. ;-\

Thanks for the fix Paolo!

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2019-12-18 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 11:20 Paolo Bonzini
2019-12-18 12:24 ` Borislav Petkov [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=20191218122400.GD24886@zn.tnic \
    --to=bp@alien8.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®