public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: [PATCH stable-5.10,5.11,5.12] x86/boot/compressed/64: Check SEV encryption in the 32-bit boot-path
Date: Tue, 18 May 2021 13:40:18 +0200	[thread overview]
Message-ID: <YKOnot8C4RKrWtXm@suse.de> (raw)
In-Reply-To: <YKOnVYLRxk9CUzTc@suse.de>

On Tue, May 18, 2021 at 01:39:02PM +0200, Joerg Roedel wrote:
> [ Upstream commit fef81c86262879d4b1176ef51a834c15b805ebb9 ]
> 
> Check whether the hypervisor reported the correct C-bit when running
> as an SEV guest. Using a wrong C-bit position could be used to leak
> sensitive data from the guest to the hypervisor.
> 
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Link: https://lkml.kernel.org/r/20210312123824.306-8-joro@8bytes.org
> ---
>  arch/x86/boot/compressed/head_64.S | 85 ++++++++++++++++++++++++++++++
>  1 file changed, 85 insertions(+)

This is compile-tested now for 5.10, 5.11 and 5.12. With 5.12 I also did
a boot-test using the 32-bit boot-path and verified it still works as
expected.

Regards,

	Joerg

  reply	other threads:[~2021-05-18 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210508032224.039CF613ED@mail.kernel.org>
2021-05-08 10:26 ` Patch "x86/boot/compressed/64: Check SEV encryption in the 32-bit boot-path" has been added to the 5.12-stable tree Greg KH
2021-05-18 11:39   ` [PATCH stable-5.10,5.11,5.12] x86/boot/compressed/64: Check SEV encryption in the 32-bit boot-path Joerg Roedel
2021-05-18 11:40     ` Joerg Roedel [this message]
2021-05-24 12:50       ` Greg KH

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=YKOnot8C4RKrWtXm@suse.de \
    --to=jroedel@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox