mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org,
	Michal Hocko <mhocko@suse.com>
Subject: Re: CVE-2023-52575: x86/srso: Fix SBPB enablement for spec_rstack_overflow=off
Date: Wed, 24 Apr 2024 14:50:36 -0700	[thread overview]
Message-ID: <2024042413-cartridge-caption-c667@gregkh> (raw)
In-Reply-To: <7c1dda50-2155-4b3c-8a87-b8669b077b30@suse.com>

On Mon, Apr 22, 2024 at 01:00:18PM +0200, Nikolay Borisov wrote:
> 
> 
> On 2.03.24 г. 23:00 ч., Greg Kroah-Hartman wrote:
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > x86/srso: Fix SBPB enablement for spec_rstack_overflow=off
> > 
> > If the user has requested no SRSO mitigation, other mitigations can use
> > the lighter-weight SBPB instead of IBPB.
> > 
> > The Linux kernel CVE team has assigned CVE-2023-52575 to this issue.
> 
> I'd like to dispute this as this isn't a CVE but a mere performance
> optimization in case spec_rstack_overflow is disabled. Without this patch in
> case spec_rstack_overflow is disabled the kernel will simply use the heavier
> ibpb but that won't have effect on correctness.

You are right, our fault.  I'll go reject this CVE now, thanks for the
review!

greg k-h

      reply	other threads:[~2024-04-24 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024030256-CVE-2023-52575-34bf@gregkh>
2024-04-22 11:00 ` Nikolay Borisov
2024-04-24 21:50   ` Greg Kroah-Hartman [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=2024042413-cartridge-caption-c667@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --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 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®