From: "Lecomte, Arnaud" <contact@arnaud-lcm.com>
To: alexei.starovoitov@gmail.com, yonghong.song@linux.dev, song@kernel.org
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@fomichev.me,
syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH bpf-next v8 3/3] bpf: fix stackmap overflow check in __bpf_get_stackid()
Date: Tue, 9 Sep 2025 13:47:42 +0100 [thread overview]
Message-ID: <93e5fc13-db88-4485-86bb-38a2cefbbf99@arnaud-lcm.com> (raw)
In-Reply-To: <20250905134833.26791-1-contact@arnaud-lcm.com>
Hi,
Can you confirm you received this one Alexei as I got an undelivered
email reply.
Cheers,
Arnaud
On 05/09/2025 14:48, Arnaud lecomte wrote:
> From: Arnaud Lecomte <contact@arnaud-lcm.com>
>
> Syzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()
> when copying stack trace data. The issue occurs when the perf trace
> contains more stack entries than the stack map bucket can hold,
> leading to an out-of-bounds write in the bucket's data array.
>
> Reported-by: syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c9b724fbb41cf2538b7b
> Fixes: ee2a098851bf ("bpf: Adjust BPF stack helper functions to accommodate skip > 0")
> Signed-off-by: Arnaud Lecomte <contact@arnaud-lcm.com>
> Acked-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> Changes in v2:
> - Fixed max_depth names across get stack id
>
> Changes in v4:
> - Removed unnecessary empty line in __bpf_get_stackid
>
> Changes in v6:
> - Added back trace_len computation in __bpf_get_stackid
>
> Changes in v7:
> - Removed usefull trace->nr assignation in bpf_get_stackid_pe
> - Added restoration of trace->nr for both kernel and user traces
> in bpf_get_stackid_pe
>
> Link to v7: https://lore.kernel.org/all/20250903234325.30212-1-contact@arnaud-lcm.com/
> ---
> kernel/bpf/stackmap.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
> index 9f3ae426ddc3..9b57b8307565 100644
> --- a/kernel/bpf/stackmap.c
> +++ b/kernel/bpf/stackmap.c
> @@ -369,6 +369,7 @@ BPF_CALL_3(bpf_get_stackid_pe, struct bpf_perf_event_data_kern *, ctx,
> {
> struct perf_event *event = ctx->event;
> struct perf_callchain_entry *trace;
> + u32 elem_size, max_depth;
> bool kernel, user;
> __u64 nr_kernel;
> int ret;
> @@ -390,15 +391,16 @@ BPF_CALL_3(bpf_get_stackid_pe, struct bpf_perf_event_data_kern *, ctx,
> return -EFAULT;
>
> nr_kernel = count_kernel_ip(trace);
> + elem_size = stack_map_data_size(map);
> + __u64 nr = trace->nr; /* save original */
>
> if (kernel) {
> - __u64 nr = trace->nr;
> -
> trace->nr = nr_kernel;
> + max_depth =
> + stack_map_calculate_max_depth(map->value_size, elem_size, flags);
> + trace->nr = min_t(u32, nr_kernel, max_depth);
> ret = __bpf_get_stackid(map, trace, flags);
>
> - /* restore nr */
> - trace->nr = nr;
> } else { /* user */
> u64 skip = flags & BPF_F_SKIP_FIELD_MASK;
>
> @@ -407,8 +409,15 @@ BPF_CALL_3(bpf_get_stackid_pe, struct bpf_perf_event_data_kern *, ctx,
> return -EFAULT;
>
> flags = (flags & ~BPF_F_SKIP_FIELD_MASK) | skip;
> + max_depth =
> + stack_map_calculate_max_depth(map->value_size, elem_size, flags);
> + trace->nr = min_t(u32, trace->nr, max_depth);
> ret = __bpf_get_stackid(map, trace, flags);
> }
> +
> + /* restore nr */
> + trace->nr = nr;
> +
> return ret;
> }
>
next prev parent reply other threads:[~2025-09-09 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:46 [PATCH bpf-next v8 1/3] bpf: refactor max_depth computation in bpf_get_stack() Arnaud lecomte
2025-09-05 13:47 ` [PATCH bpf-next v8 2/3] bpf: clean-up bounds checking in __bpf_get_stack Arnaud lecomte
2025-09-05 13:48 ` [PATCH bpf-next v8 3/3] bpf: fix stackmap overflow check in __bpf_get_stackid() Arnaud lecomte
2025-09-09 12:47 ` Lecomte, Arnaud [this message]
2025-09-09 16:41 ` Song Liu
2025-09-10 20:01 ` Arnaud Lecomte
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=93e5fc13-db88-4485-86bb-38a2cefbbf99@arnaud-lcm.com \
--to=contact@arnaud-lcm.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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
all inboxes | Powered by JetHome®