From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <almagui@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev,
bpf@vger.kernel.org, nathan@kernel.org
Subject: Re: [PATCH bpf] libbpf: Fix use-after-free in btf__add_type
Date: Mon, 02 Nov 2026 22:50:06 +0000 [thread overview]
Message-ID: <179365980656.707305.4291574922121465875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261102185839.1190122-1-almagui@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 2 Nov 2026 18:58:39 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> For every string btf_rewrite_str() does:
>
> off = btf__add_str(p->dst, btf__str_by_offset(p->src, *str_off));
>
> When the string belongs to the base, the pointer goes into the raw data
> of the base. btf__add_str() looks the string up in the base first,
> btf__find_str() calls btf_ensure_modifiable() on the base, and that
> frees the raw data. Then strset__find_str() reads the freed string.
>
> [...]
Here is the summary with links:
- [bpf] libbpf: Fix use-after-free in btf__add_type
https://git.kernel.org/bpf/bpf/c/9abe2c42ecab
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-02 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 18:58 [PATCH bpf] libbpf: Fix use-after-free in btf__add_type Alan Maguire
2026-11-02 19:43 ` bot+bpf-ci
2026-11-02 22:50 ` patchwork-bot+netdevbpf [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=179365980656.707305.4291574922121465875.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almagui@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nathan@kernel.org \
--cc=song@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 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.