From: Greg KH <gregkh@linuxfoundation.org>
To: 하태구 <hataegu0826@gmail.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [STABLE REQUEST] bpf: backport de36adca6346 to 7.1.y
Date: Tue, 25 Aug 2026 10:25:00 +0200 [thread overview]
Message-ID: <2026082526-remindful-aids-773b@gregkh> (raw)
In-Reply-To: <CAPa51zmwhbD2Xc1kFJY8HmpG-DY3OsK=G=h2Yn5ismeGCxo==g@mail.gmail.com>
On Tue, Aug 25, 2026 at 04:00:34AM +0900, 하태구 wrote:
> Hello,
>
> Please consider backporting the following upstream commit to Linux 7.1.y:
>
> de36adca634634c205a9eb8b56a28175ab7abf5f
> ("bpf: reject overlarge global subprog argument sizes")
>
> The issue was introduced by:
>
> 2cb27158adb3 ("bpf: poison dead stack slots")
>
> which is present in Linux 7.1.
>
> The fix rejects BTF-derived global subprogram argument sizes larger
> than S32_MAX. Without the check, the caller-side PTR_TO_STACK
> validation can interpret an overlarge size differently from the
> callee-side PTR_TO_MEM state, potentially allowing the verifier to
> validate accesses outside the actual stack object.
>
> The upstream commit includes a selftest and applies cleanly to the
> current linux-7.1.y tree. The fix is present in Linux 7.2 but is not
> present in Linux 7.1.10 or the current 7.1 stable queue.
>
> Upstream commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de36adca634634c205a9eb8b56a28175ab7abf5f
>
> Target stable series:
>
> 7.1.y
It does not actually build properly, how did you test this? Please
provide a working backport that has been tested if you wish to see this
added to the 7.1.y tree.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-25 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 19:00 [STABLE REQUEST] bpf: backport de36adca6346 to 7.1.y 하태구
2026-08-25 8:25 ` Greg KH [this message]
2026-08-25 14:24 ` [PATCH 7.1.y] bpf: reject overlarge global subprog argument sizes Taegu Ha
2026-08-27 5:17 ` 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=2026082526-remindful-aids-773b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hataegu0826@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox