From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2024-35802: x86/sev: Fix position dependent variable references in startup code
Date: Thu, 23 May 2024 14:38:44 +0200 [thread overview]
Message-ID: <2024052327-cider-finance-d040@gregkh> (raw)
In-Reply-To: <d6981cc9-ea89-47fb-9084-267eba05c7a1@suse.com>
On Thu, May 23, 2024 at 03:21:05PM +0300, Nikolay Borisov wrote:
>
>
> On 23.05.24 г. 15:17 ч., Greg Kroah-Hartman wrote:
> > On Thu, May 23, 2024 at 03:01:56PM +0300, Nikolay Borisov wrote:
> > >
> > >
> > > On 23.05.24 г. 14:21 ч., Greg Kroah-Hartman wrote:
> > > > Isn't crashing SEV guests a problem with "availability"? That term
> > > > comes from the CVE definition of what we need to mark as a CVE, which is
> > > > why this one was picked.
> > >
> > > But availability has never been one of the tenets of CoCo, in fact in
> > > sev-snp/tdx the VMM is explicitly considered outside of the TCB so
> > > availability cannot be guaranteed.
> >
> > This has nothing to do with CoCo (but really, ability of the host to
> > crash the guest seems like it should be as I would assume that CoCo
> > guests would want to be able to be run...)
> >
> > Official CVE definition of vulnerability from cve.org:
> > An instance of one or more weaknesses in a Product that can be
> > exploited, causing a negative impact to confidentiality, integrity, or
>
> I don't see how this is exactly "explotaible" i.e if a guest is run and it
> crashes during bootup it simply won't run. Can this be considered active
> exploitation of an issue?
Isn't preventing a guest from running something that causes a lack of
avaiability? Again, that's why we picked this commit, it keeps the
system from working properly as expected.
thanks,
greg k-h
next prev parent reply other threads:[~2024-05-23 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:23 CVE-2024-35802: x86/sev: Fix position dependent variable references in startup code Greg Kroah-Hartman
2024-05-23 11:14 ` Nikolay Borisov
2024-05-23 11:21 ` Greg Kroah-Hartman
2024-05-23 12:01 ` Nikolay Borisov
2024-05-23 12:17 ` Greg Kroah-Hartman
2024-05-23 12:21 ` Nikolay Borisov
2024-05-23 12:38 ` Greg Kroah-Hartman [this message]
2024-05-28 8:51 ` Michal Hocko
2024-05-28 19:08 ` Greg Kroah-Hartman
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=2024052327-cider-finance-d040@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.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 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.