From: Artem Dinaburg <artem@trailofbits.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: Please consider these upstream CVE fixes for 6.6.y
Date: Sun, 30 Aug 2026 04:27:33 -0400 [thread overview]
Message-ID: <20260830082733.35424-1-artem@trailofbits.com> (raw)
Hi Greg and Sasha,
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.
I applied the current 6.6.y queue to v6.6.155, then cherry-picked this set
without changes. The x86_64 allmodconfig kernel and modules built without
warnings with WERROR enabled. The PowerPC target compiled cleanly after I
enabled the related config options. I did not runtime-test these fixes.
Could you please queue these commits for 6.6.y?
0f022d32c3eca477fbf79a205243a6123ed0fe11 (CVE-2024-27010)
net/sched: Fix mirred deadlock on device recursion
d7f01649f4eaf1878472d3d3f480ae1e50d98f6c (CVE-2024-39478)
crypto: starfive - Do not free stack buffer
d48e1dea3931de64c26717adc2b89743c7ab6594 (CVE-2024-50225)
btrfs: fix error propagation of split bios
dbc30a57bd8e026995e9fa8e8c31cffd18542c01 (CVE-2026-64070)
powerpc/hv-gpci: fix preempt count leak in sysfs show paths
I used Codex to compare the histories and run the builds. I checked the
final list against vulns.git, the branch history, and stable-queue.
Assisted-by: Codex:GPT-5.6
Thanks,
Artem Dinaburg
Trail of Bits
next reply other threads:[~2026-08-30 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 8:27 Artem Dinaburg [this message]
2026-08-31 1:39 ` Please consider these upstream CVE fixes for 6.6.y Sasha Levin
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=20260830082733.35424-1-artem@trailofbits.com \
--to=artem@trailofbits.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@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.