From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
daniel@iogearbox.net, info@starlabs.sg, ast@kernel.org,
lulie@linux.alibaba.com, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, mykolal@fb.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, dust.li@linux.alibaba.com
Subject: Re: [PATCH 6.6.y/6.12.y/6.18.y 0/2] bpf: Fix ld_{abs,ind} failure path analysis in subprogs
Date: Fri, 24 Jul 2026 07:22:33 -0400 [thread overview]
Message-ID: <20260724105500.stable-0001@kernel.org> (raw)
In-Reply-To: <20260722073908.72382-1-lulie@linux.alibaba.com>
> Backport of the CVE-2026-53090 fix.
>
> 1/2 ee861486e377, the CVE fix.
> 2/2 e0fcb42bc6f4, selftests for the fix.
Queued the series for 6.6, 6.12, and 6.18, thanks.
One follow-up: the Fixes commit 09b28d76eac4 ("bpf: Add abnormal return
checks.") is also present in 6.1, 5.15 and 5.10, and the fix is absent there,
so those trees are affected as well but were not covered by this submission.
They likely need a further adaptation. Could you extend coverage with adapted
backports for 6.1/5.15/5.10?
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-24 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 7:39 [PATCH 6.6.y/6.12.y/6.18.y 0/2] bpf: Fix ld_{abs,ind} failure path analysis in subprogs Philo Lu
2026-07-22 7:39 ` [PATCH 6.6.y/6.12.y/6.18.y 1/2] " Philo Lu
2026-07-22 8:49 ` Pu Lehui
2026-07-22 7:39 ` [PATCH 6.6.y/6.12.y/6.18.y 2/2] selftests/bpf: Add tests for ld_{abs,ind} failure path " Philo Lu
2026-07-22 8:50 ` Pu Lehui
2026-07-24 11:22 ` Sasha Levin [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=20260724105500.stable-0001@kernel.org \
--to=sashal@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dust.li@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=info@starlabs.sg \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lulie@linux.alibaba.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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