From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: [PATCHES v2 0/4] perf tools: Fix OOB reads, NULL deref, and resource leaks
Date: Thu, 4 Jun 2026 17:49:15 -0300 [thread overview]
Message-ID: <20260604204921.1707333-1-acme@kernel.org> (raw)
Hi,
Four pre-existing bugs found by sashiko-bot during AI-assisted review
of the perf-data-validation hardening series. All are independent of
that series -- they are latent bugs in surrounding code exposed during
review.
1. test_bit(sample->cpu, cpu_bitmap) reads out of bounds when
PERF_SAMPLE_CPU is absent (sample->cpu == (u32)-1) in annotate,
diff, report, and sched timehist.
2. Thread reference leak in perf sched latency_switch_event() -- one
error path does 'return -1' instead of 'goto out_put'.
3. NULL pointer dereference in perf sched latency_runtime_event() --
thread_atoms_search() called before the NULL check on the thread
returned by machine__findnew_thread().
4. Heap buffer overflow in perf sched map --compact mode --
comp_cpus allocated based on host CPU count but indexed using a
MAX_CPUS-sized bitmap, overflowing when analyzing recordings from
machines with more CPUs than the host. Also fixes the sizeof
mismatch from the int-to-struct perf_cpu type change, removes the
now-dead sysconf(_SC_NPROCESSORS_CONF) initialization, and fixes
an off-by-one in the non-compact path where max_cpu (0-based
index) was used as cpus_nr (count) without adding 1.
All four require crafted or unusual perf.data inputs to trigger.
Verified with gcc and clang builds, checkpatch, and perf test.
Changes in v2:
- Patch 4: fix off-by-one in non-compact path — max_cpu.cpu is a
0-based index, needs + 1 when used as cpus_nr (count).
Reported by sashiko-bot.
Arnaldo Carvalho de Melo (4):
perf tools: Guard test_bit from out-of-bounds sample CPU
perf sched: Fix thread reference leak in latency_switch_event
perf sched: Fix NULL dereference in latency_runtime_event
perf sched: Fix comp_cpus heap overflow with cross-machine recordings
tools/perf/builtin-annotate.c | 3 ++-
tools/perf/builtin-diff.c | 3 ++-
tools/perf/builtin-report.c | 3 ++-
tools/perf/builtin-sched.c | 18 ++++++++++--------
4 files changed, 16 insertions(+), 11 deletions(-)
Developed with AI assistance (Claude/sashiko), tagged in commits.
Thanks a lot,
- Arnaldo
next reply other threads:[~2026-06-04 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 20:49 Arnaldo Carvalho de Melo [this message]
2026-06-04 20:49 ` [PATCH 1/4] perf tools: Guard test_bit from out-of-bounds sample CPU Arnaldo Carvalho de Melo
2026-06-04 21:09 ` sashiko-bot
2026-06-04 21:15 ` Arnaldo Carvalho de Melo
2026-06-04 20:49 ` [PATCH 2/4] perf sched: Fix thread reference leak in latency_switch_event Arnaldo Carvalho de Melo
2026-06-04 20:49 ` [PATCH 3/4] perf sched: Fix NULL dereference in latency_runtime_event Arnaldo Carvalho de Melo
2026-06-04 20:49 ` [PATCH 4/4] perf sched: Fix comp_cpus heap overflow with cross-machine recordings Arnaldo Carvalho de Melo
2026-06-04 22:08 ` [PATCHES v2 0/4] perf tools: Fix OOB reads, NULL deref, and resource leaks 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=20260604204921.1707333-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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