From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52575: x86/srso: Fix SBPB enablement for spec_rstack_overflow=off
Date: Sat, 2 Mar 2024 23:00:09 +0100 [thread overview]
Message-ID: <2024030256-CVE-2023-52575-34bf@gregkh> (raw)
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.
Affected and fixed versions
===========================
Issue introduced in 5.10.189 with commit 8457fb5740b1 and fixed in 5.10.198 with commit ae806c74c063
Issue introduced in 5.15.125 with commit 153f9a7b02d4 and fixed in 5.15.134 with commit 13ea4b92e875
Issue introduced in 6.1.44 with commit 4f25355540ad and fixed in 6.1.56 with commit adbcec23c842
Issue introduced in 6.5 with commit fb3bd914b3ec and fixed in 6.5.6 with commit e3cb8b2c391b
Issue introduced in 6.5 with commit fb3bd914b3ec and fixed in 6.6 with commit 01b057b2f4cc
Please see https://www.kernel.org or a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-52575
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/x86/kernel/cpu/bugs.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/ae806c74c0634b0c23855066d8ba28d850fd1260
https://git.kernel.org/stable/c/13ea4b92e8759d2f6c330a73cde31ad9c313021b
https://git.kernel.org/stable/c/adbcec23c8423e3d5df1839c5ae91599dcf703cb
https://git.kernel.org/stable/c/e3cb8b2c391b1f287eb76df4ba37880f4ea56d8a
https://git.kernel.org/stable/c/01b057b2f4cc2d905a0bd92195657dbd9a7005ab
next reply other threads:[~2024-03-02 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 22:00 Greg Kroah-Hartman [this message]
[not found] ` <7c1dda50-2155-4b3c-8a87-b8669b077b30@suse.com>
2024-04-24 21:50 ` CVE-2023-52575: x86/srso: Fix SBPB enablement for spec_rstack_overflow=off 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=2024030256-CVE-2023-52575-34bf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).