From: Greg Kroah-Hartman <gregkh@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
linux-kernel@vger.kernel.org,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection
Date: Fri, 7 Aug 2026 08:45:45 +0200 [thread overview]
Message-ID: <2026080720-surging-tributary-b2ef@gregkh> (raw)
In-Reply-To: <20260807063119.GJanV7tw1Zkcuy3Byr@fat_crate.local>
On Thu, Aug 06, 2026 at 11:31:19PM -0700, Borislav Petkov wrote:
> On Thu, Aug 06, 2026 at 03:42:00PM -0700, Borislav Petkov wrote:
> > On Thu, Aug 06, 2026 at 11:42:59PM +0200, Thomas Lamprecht wrote:
> > > > Fixed in 5.10.263 with commit 9de1a49e8f1fbf7c372902573a27a97d4ab4d0af
> > > > Fixed in 5.15.214 with commit 9c0b8105e919be5208c81d5516a194a28c58fe1e
> > > > Fixed in 6.1.181 with commit 95b08cdd603fe79d2e9d5212fbb13d577c835f4f
> > > > Fixed in 6.6.149 with commit 608c8f5dccaaf8b8d2b28c0fbdd439d144be62b0
> > >
> > > I hope I did not overlooked something, but at least the 6.6 backport seems
> > > broken to me as it #ifdef guards the fixes on CONFIG_MITIGATION_SRSO, but that
> > > config name is only used in v6.9+ since a033eec9a06ce ("x86/bugs: Rename
> > > CONFIG_CPU_SRSO => CONFIG_MITIGATION_SRSO") [0] FWICT, i.e. before
> > > that version it was named CONFIG_CPU_SRSO. So shouldn't be that be used here
> > > for all the older pre-v6.9 backports above?
> >
> > Thanks for letting me know - I'm fixing.
>
> Hopefully fixed kernels are out now. Sorry for the trouble.
Thanks for the quick response, and for Thomas the review. If there are
any issues with the newly released kernels now, please let us know.
thanks,
greg k-h
prev parent reply other threads:[~2026-08-07 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026080631-CVE-2026-68480-ad40@gregkh>
2026-08-06 21:42 ` Thomas Lamprecht
2026-08-06 22:42 ` Borislav Petkov
2026-08-07 6:31 ` Borislav Petkov
2026-08-07 6:45 ` 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=2026080720-surging-tributary-b2ef@gregkh \
--to=gregkh@kernel.org \
--cc=bp@alien8.de \
--cc=f.gruenbichler@proxmox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t.lamprecht@proxmox.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®