From: sashiko-bot@kernel.org
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 2/3] perf symbol: Add missing symsrc__destroy() for libbfd
Date: Sat, 10 Oct 2026 18:34:56 +0000 [thread overview]
Message-ID: <sashiko-outbox-166826@kernel.org> (raw)
In-Reply-To: <20261010182439.9732-2-namhyung@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] perf: double free and UAF in libbfd fallback logic
--
commit 27e7b4b66a3038201c422641092c060f7b466328
Author: Namhyung Kim <namhyung@kernel.org>
perf symbol: Add missing symsrc__destroy() for libbfd
This commit aims to prevent memory leaks and symbol overwrites by destroying
any pending syms_ss when libbfd successfully loads symbols.
Closes: https://lore.kernel.org/r/sashiko-outbox-162540@kernel.org
> diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
> index 6e327eaec8c0e..5e63c3477570c 100644
> --- a/tools/perf/util/symbol.c
> +++ b/tools/perf/util/symbol.c
> @@ -1925,6 +1925,10 @@ int dso__load(struct dso *dso, struct map *map)
> nsinfo__mountns_enter(dso__nsinfo(dso), &nsc);
>
> if (bfdrc > 0) {
> + if (syms_ss) {
> + symsrc__destroy(syms_ss);
> + syms_ss = NULL;
> + }
[Severity: High]
Can this sequence lead to a use-after-free and double free later in the
function?
If syms_ss and runtime_ss were both set to point to the same symsrc object
in an earlier iteration of the candidate debug images loop, this block
destroys the object and clears syms_ss, but leaves runtime_ss pointing to
the now freed memory. The object also remains tracked in the ss_ array.
After the loop breaks, could the fallback logic in dso__load() resurrect the
destroyed object:
if (runtime_ss && !syms_ss) {
syms_ss = runtime_ss;
}
This appears to lead to dso__load_sym() being called with the destroyed
syms_ss object, which would cause a use-after-free and overwrite the
successful ret = 1 result from BFD:
if (syms_ss)
ret = dso__load_sym(dso, map, syms_ss, runtime_ss, kmod);
Finally, since the destroyed object was never removed from the ss_ array,
would the cleanup block at the end of the function trigger a double-free?
for (; ss_pos > 0; ss_pos--)
symsrc__destroy(&ss_[ss_pos - 1]);
> ret = 1;
> break;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261010182439.9732-1-namhyung@kernel.org?part=2
next prev parent reply other threads:[~2026-10-10 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 18:24 [PATCH v2 1/3] perf symbol: Fix symbol loading from libbfd Namhyung Kim
2026-10-10 18:24 ` [PATCH v2 2/3] perf symbol: Add missing symsrc__destroy() for libbfd Namhyung Kim
2026-10-10 18:34 ` sashiko-bot [this message]
2026-10-10 19:01 ` Namhyung Kim
2026-10-10 18:24 ` [PATCH v2 3/3] perf symbol: Set dso symtab type " Namhyung Kim
2026-10-10 18:34 ` sashiko-bot
2026-10-10 19:02 ` Namhyung Kim
2026-10-10 18:36 ` [PATCH v2 1/3] perf symbol: Fix symbol loading from libbfd sashiko-bot
2026-10-10 19:00 ` Namhyung Kim
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=sashiko-outbox-166826@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sashiko-reviews@lists.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