All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] kvm: vmx: Scrub hardware GPRs at VM-exit
Date: Wed, 10 Jan 2018 13:17:20 +0100	[thread overview]
Message-ID: <20180110121720.GD12483@kroah.com> (raw)
In-Reply-To: <20180109084620.24712-1-pbonzini@redhat.com>

On Tue, Jan 09, 2018 at 09:46:20AM +0100, Paolo Bonzini wrote:
> From: Jim Mattson <jmattson@google.com>
> 
> [ upstream commit 0cb5b30698fdc8f6b4646012e3acb4ddce430788 ]
> 
> Guest GPR values are live in the hardware GPRs at VM-exit.  Do not
> leave any guest values in hardware GPRs after the guest GPR values are
> saved to the vcpu_vmx structure.
> 
> This is a partial mitigation for CVE 2017-5715 and CVE 2017-5753.
> Specifically, it defeats the Project Zero PoC for CVE 2017-5715.
> 
> Suggested-by: Eric Northup <digitaleric@google.com>
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Reviewed-by: Eric Northup <digitaleric@google.com>
> Reviewed-by: Benjamin Serebrin <serebrin@google.com>
> Reviewed-by: Andrew Honig <ahonig@google.com>
> [Paolo: Add AMD bits, Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>]
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Now applied, thanks.

greg k-h

  reply	other threads:[~2018-01-10 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09  8:46 [PATCH] kvm: vmx: Scrub hardware GPRs at VM-exit Paolo Bonzini
2018-01-10 12:17 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 22:31 Jim Mattson
2018-01-07 10:40 ` Jan Kiszka
2018-01-08  8:58   ` Jack Wang
2018-01-08  9:57     ` Jan Kiszka
2018-01-08 14:53       ` Paolo Bonzini
2018-01-09  8:27         ` Jack Wang
2018-01-09  8:43           ` Paolo Bonzini
2018-01-09  8:49             ` Jack Wang
2018-02-11  8:42         ` Wanpeng Li

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=20180110121720.GD12483@kroah.com \
    --to=greg@kroah.com \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.