From: Salvatore Bonaccorso <carnil@debian.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
David Kaplan <David.Kaplan@amd.com>
Subject: CVE-2026-68480 mitigations for older stable series (was: Re: Linux 6.6.149)
Date: Fri, 7 Aug 2026 06:22:50 +0200 [thread overview]
Message-ID: <anVdmsj0Ko294nBP@eldamar.lan> (raw)
In-Reply-To: <2026080618-mulch-nullify-723f@gregkh>
Hi Greg, hi Borislav,
On Thu, Aug 06, 2026 at 07:32:17PM +0200, Greg Kroah-Hartman wrote:
> I'm announcing the release of the 6.6.149 kernel.
>
> All users of the 6.6 kernel series must upgrade.
>
> The updated 6.6.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.6.y
> and can be browsed at the normal kernel.org git web browser:
> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
It got mentioned outside of the stable list that the backports of
7e7f81cf6f5c ("x86/bugs: Make Safe-RET robust against interrupt
injection") to address CVE-2026-68480 will not work. So raising the
problem here.
In fact at least they depend on CONFIG_MITIGATION_SRSO, which only was
renamed in a033eec9a06c ("x86/bugs: Rename CONFIG_CPU_SRSO
=> CONFIG_MITIGATION_SRSO") v6.9-rc1, correct?
Borislav, can you have a look for the older backports?
Regards,
Salvatore
next prev parent reply other threads:[~2026-08-07 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:32 Linux 6.6.149 Greg Kroah-Hartman
2026-08-06 17:32 ` Greg Kroah-Hartman
2026-08-07 4:22 ` Salvatore Bonaccorso [this message]
2026-08-07 4:30 ` CVE-2026-68480 mitigations for older stable series (was: Re: Linux 6.6.149) Borislav Petkov
2026-08-07 6:31 ` Borislav Petkov
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=anVdmsj0Ko294nBP@eldamar.lan \
--to=carnil@debian.org \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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.