From: Arnaud Lecomte <contact@arnaud-lcm.com>
To: Yonghong Song <yonghong.song@linux.dev>, song@kernel.org
Cc: jolsa@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com
Subject: Re: [PATCH] bpf: fix stackmap overflow check in __bpf_get_stackid()
Date: Tue, 29 Jul 2025 17:54:45 +0100 [thread overview]
Message-ID: <f86d659b-29f2-4f78-b2e9-8b667edfaa8e@arnaud-lcm.com> (raw)
In-Reply-To: <004ec202-cbe7-4108-b6ac-1d947a5a54b8@linux.dev>
Good catch thanks Yonghong, sending rev2.
On 29/07/2025 17:21, Yonghong Song wrote:
>
>
> On 7/29/25 2:19 AM, Arnaud Lecomte wrote:
>> 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.
>> For build_id mode, we use sizeof(struct bpf_stack_build_id)
>> to determine capacity, and for normal mode we use sizeof(u64).
>>
>> Reported-by: syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=c9b724fbb41cf2538b7b
>> Tested-by: syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com
>> Signed-off-by: Arnaud Lecomte <contact@arnaud-lcm.com>
>> ---
>> kernel/bpf/stackmap.c | 12 +++++++++++-
>> 1 file changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
>> index 3615c06b7dfa..0f9f6e4b6fe9 100644
>> --- a/kernel/bpf/stackmap.c
>> +++ b/kernel/bpf/stackmap.c
>> @@ -230,7 +230,7 @@ static long __bpf_get_stackid(struct bpf_map *map,
>> struct bpf_stack_map *smap = container_of(map, struct
>> bpf_stack_map, map);
>> struct stack_map_bucket *bucket, *new_bucket, *old_bucket;
>> u32 skip = flags & BPF_F_SKIP_FIELD_MASK;
>> - u32 hash, id, trace_nr, trace_len, i;
>> + u32 hash, id, trace_nr, trace_len, i, max_depth;
>> bool user = flags & BPF_F_USER_STACK;
>> u64 *ips;
>> bool hash_matches;
>> @@ -241,6 +241,16 @@ static long __bpf_get_stackid(struct bpf_map *map,
>> trace_nr = trace->nr - skip;
>> trace_len = trace_nr * sizeof(u64);
>> +
>> + /* Clamp the trace to max allowed depth */
>> + if (stack_map_use_build_id(map))
>> + max_depth = smap->map.value_size / sizeof(struct
>> bpf_stack_build_id);
>> + else
>> + max_depth = smap->map.value_size / sizeof(u64);
>
> Replace the above with
> max_depth = smap->map.value_size / stack_map_data_size(map)
> ?
>
>> +
>> + if (trace_nr > max_depth)
>> + trace_nr = max_depth;
>> +
>> ips = trace->ip + skip;
>> hash = jhash2((u32 *)ips, trace_len / sizeof(u32), 0);
>> id = hash & (smap->n_buckets - 1);
>
>
prev parent reply other threads:[~2025-07-29 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 9:19 Arnaud Lecomte
2025-07-29 16:21 ` Yonghong Song
2025-07-29 16:54 ` Arnaud Lecomte [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=f86d659b-29f2-4f78-b2e9-8b667edfaa8e@arnaud-lcm.com \
--to=contact@arnaud-lcm.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=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®