From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Artem Dinaburg <artem@trailofbits.com>
Subject: Re: Please consider these upstream CVE fixes for 6.6.y
Date: Sun, 30 Aug 2026 21:39:16 -0400 [thread overview]
Message-ID: <20260830195500.0011-1-sashal@kernel.org> (raw)
In-Reply-To: <20260830082733.35424-1-artem@trailofbits.com>
> Thanks for carrying the earlier 6.1.y fixes into the newer trees. After
> dropping them, these four mainline fixes remain absent from 6.6.y and its
> current stable queue. Linux CNA records mark v6.6.155 affected for each
> CVE. Every newer tree has the first three fixes. The last remains absent
> from 6.12.y and 6.18.y.
Queued the mirred deadlock fix and its noop_qdisc owner follow-up plus
the starfive fix for 6.6.y, and the hv-gpci fix for 6.18.y, 6.12.y and
6.6.y. Thanks.
Dropped the btrfs one - it doesn't build on 6.6 riscv, 1-byte cmpxchg
isn't supported there.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-31 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 8:27 Please consider these upstream CVE fixes for 6.6.y Artem Dinaburg
2026-08-31 1:39 ` Sasha Levin [this message]
2026-09-01 1:21 ` Sasha Levin
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=20260830195500.0011-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=artem@trailofbits.com \
--cc=gregkh@linuxfoundation.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.