From: sashiko-bot@kernel.org
To: "Arnaldo Carvalho de Melo" <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 08/11] perf bpf: Use scnprintf() in snprintf_hex() and synthesize_bpf_prog_name()
Date: Tue, 09 Jun 2026 01:18:18 +0000 [thread overview]
Message-ID: <20260609011818.B00151F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260609010526.1998472-9-acme@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Accumulation of `snprintf` return values combined with fixed increments causes buffer size integer underflows, leading to a stack buffer overflow in `perf_pmu__for_each_event`.
--
commit 9c31711b5b63e0f7c6e422153e389b761e114baf
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
perf bpf: Use scnprintf() in snprintf_hex() and synthesize_bpf_prog_name()
This patch fixes a potential buffer overflow by switching from snprintf() to
scnprintf() during formatted output accumulation. This prevents the remaining
buffer size from underflowing if the output is truncated.
> diff --git a/tools/perf/util/bpf-event.c b/tools/perf/util/bpf-event.c
> index a27945c279efb..2c09842469f1f 100644
> --- a/tools/perf/util/bpf-event.c
> +++ b/tools/perf/util/bpf-event.c
[ ... ]
> @@ -153,9 +153,10 @@ static int synthesize_bpf_prog_name(char *buf, int size,
> short_name = info->name;
> } else
> short_name = "F";
> - if (short_name)
> - name_len += snprintf(buf + name_len, size - name_len,
> - "_%s", short_name);
> + if (short_name) {
> + name_len += scnprintf(buf + name_len, size - name_len,
> + "_%s", short_name);
> + }
> return name_len;
> }
While we are fixing snprintf() accumulations here, there is a similar
pre-existing issue in tools/perf/util/pmu.c:
tools/perf/util/pmu.c:perf_pmu__for_each_event() {
...
info.scale_unit = NULL;
if (strlen(event->unit) || event->scale != 1.0) {
info.scale_unit = buf + buf_used;
buf_used += snprintf(buf + buf_used, sizeof(buf) - buf_used,
"%G%s", event->scale, event->unit) + 1;
}
info.desc = event->desc;
info.long_desc = event->long_desc;
info.encoding_desc = buf + buf_used;
buf_used += snprintf(buf + buf_used, sizeof(buf) - buf_used,
"%.*s/%s/", (int)pmu_name_len, info.pmu_name, event->terms) + 1;
...
}
[Severity: High]
This is a pre-existing issue, but the same pattern is present in
perf_pmu__for_each_event().
Because snprintf() returns the length it would have written rather than the
amount actually written, and we unconditionally add 1 to it, buf_used can exceed
sizeof(buf).
When buf_used exceeds sizeof(buf), sizeof(buf) - buf_used will underflow to a
large positive size.
Could the subsequent snprintf() call use this massive size limit and write to
the out-of-bounds pointer buf + buf_used, overflowing buf[]?
Other similar bugs in hwmon_pmu.c and hist.c appear to be fixed in subsequent
patches of this series, but pmu.c seems to remain vulnerable at the end of the
series.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609010526.1998472-1-acme@kernel.org?part=8
next prev parent reply other threads:[~2026-06-09 1:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 1:05 [PATCHES v4 00/11] perf tools: Assorted fixes Arnaldo Carvalho de Melo
2026-06-09 1:05 ` [PATCH 01/11] perf tools: Fix get_max_num() size_t underflow on empty sysfs file Arnaldo Carvalho de Melo
2026-06-09 1:24 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 02/11] perf tools: Use scnprintf() in cpu_map__snprint() to prevent overflow Arnaldo Carvalho de Melo
2026-06-09 1:05 ` [PATCH 03/11] perf tools: Use perf_env__get_cpu_topology() in machine__resolve() Arnaldo Carvalho de Melo
2026-06-09 1:22 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 04/11] perf tools: NULL bitmap pointers after bitmap_free() Arnaldo Carvalho de Melo
2026-06-09 1:23 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 05/11] perf sched: Bounds-check prio before test_bit() in timehist Arnaldo Carvalho de Melo
2026-06-09 1:05 ` [PATCH 06/11] perf sched: Fix idle-hist callchain display using wrong rb_first variant Arnaldo Carvalho de Melo
2026-06-09 1:18 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 07/11] perf tools: Add O_CLOEXEC to open() calls in DSO and ELF code Arnaldo Carvalho de Melo
2026-06-09 1:16 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 08/11] perf bpf: Use scnprintf() in snprintf_hex() and synthesize_bpf_prog_name() Arnaldo Carvalho de Melo
2026-06-09 1:18 ` sashiko-bot [this message]
2026-06-09 1:05 ` [PATCH 09/11] perf hists: Fix snprintf() in hists__scnprintf_title() UID filter path Arnaldo Carvalho de Melo
2026-06-09 1:23 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 10/11] perf tools: Use scnprintf() in build_id__snprintf() and hwmon read_events() Arnaldo Carvalho de Melo
2026-06-09 1:17 ` sashiko-bot
2026-06-09 1:05 ` [PATCH 11/11] libperf: Document code simplification case for widening struct perf_cpu Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2026-06-08 20:17 [PATCHES v3 00/11] perf tools: Assorted fixes Arnaldo Carvalho de Melo
2026-06-08 20:17 ` [PATCH 08/11] perf bpf: Use scnprintf() in snprintf_hex() and synthesize_bpf_prog_name() Arnaldo Carvalho de Melo
2026-06-08 20:50 ` sashiko-bot
2026-06-08 22:01 ` Ian Rogers
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=20260609011818.B00151F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.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