From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
sashiko-bot@kernel.org,
"Claude Opus 4.6 (1M context)" <noreply@anthropic.com>
Subject: Re: [PATCH 26/28] perf timechart: Bounds check cpu_id and fix topology_map allocation
Date: Tue, 12 May 2026 16:48:24 -0300 [thread overview]
Message-ID: <agOECAaMwN_mQekU@x1> (raw)
In-Reply-To: <CAP-5=fU11BRywA+YaRV5X6iLw0zfm5ju2B9PuZ6yJn8aAtv4XQ@mail.gmail.com>
On Tue, May 12, 2026 at 11:32:48AM -0700, Ian Rogers wrote:
> On Sat, May 9, 2026 at 8:37 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > The cpu_idle, cpu_frequency, power_start, and power_frequency
> > tracepoint handlers extract cpu_id from the event payload via
> > evsel__intval() and use it directly as an array index into
> > cpus_cstate_start_times[] and cpus_pstate_start_times[], which
> > are allocated with MAX_CPUS (4096) entries.
> >
> > Unlike sample->cpu which is validated in perf_session__deliver_event(),
> > cpu_id comes from the tracepoint data and is never bounds checked.
> > A crafted perf.data with a malicious cpu_id in a tracepoint event
> > causes out-of-bounds array accesses.
> >
> > Validate cpu_id against tchart->numcpus (nr_cpus_avail from the
> > file header) and reject the event with an error if it is out of
> > range, as this indicates a corrupted or crafted file.
> >
> > The power_end handler uses sample->cpu (not a tracepoint cpu_id
> > field). Add a bounds check there too since a crafted file could
> > omit PERF_SAMPLE_CPU, leaving sample->cpu as the (u32)-1 sentinel
> > which would cause out-of-bounds access in c_state_end().
> >
> > Also validate sample->cpu in sched_switch and sched_wakeup
> > handlers, which store it in cpu_sample structs later used as
> > array indices into topology_map[] during SVG generation.
> >
> > Fix svg_build_topology_map() to allocate topology_map using
> > nr_cpus_avail instead of nr_cpus_online. When offline CPUs exist,
> > nr_cpus_online < nr_cpus_avail, and a valid cpu_id that passes
> > the numcpus check could still exceed the topology_map allocation,
> > causing a heap out-of-bounds read in cpu2y(). Reject negative CPU
> > values in str_to_bitmap() to prevent perf_cpu_map__new("") on an
> > empty topology string from passing -1 to __set_bit(), which would
> > write at offset ULONG_MAX/BITS_PER_LONG.
> >
> > Fix the pre-existing backtrace memory leak: change the
> > tracepoint_handler typedef to pass const char **backtrace
> > (pointer-to-pointer). Handlers that consume the string
> > (sched_switch, sched_wakeup) set *backtrace = NULL to claim
> > ownership. The caller always calls free() after the handler
> > returns — if ownership was taken the pointer is NULL and
> > free(NULL) is a no-op. Skip cat_backtrace() entirely when
> > tchart->with_backtrace is not set.
> >
> > Cap tchart->numcpus at MAX_CPUS in the HEADER_NRCPUS callback
> > so the bounds check cannot exceed the array allocation size.
>
> So there are some overlaps with the changes in:
> https://lore.kernel.org/lkml/20260413041143.1736055-18-irogers@google.com/
> I'll repost the series that Namhyung started merging. It would be good
> to rebase these changes on that.
Please rebase and resubmit, I can adjust before sending v2 for the perf
data validation series.
- Arnaldo
next prev parent reply other threads:[~2026-05-12 19:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 3:33 [PATCH 00/28] perf: Harden perf.data parsing against crafted/corrupted files Arnaldo Carvalho de Melo
2026-05-10 3:33 ` [PATCH 01/28] perf session: Add minimum event size validation table Arnaldo Carvalho de Melo
2026-05-11 19:01 ` Ian Rogers
2026-05-10 3:33 ` [PATCH 02/28] perf tools: Fix event_contains() macro to verify full field extent Arnaldo Carvalho de Melo
2026-05-11 23:46 ` sashiko-bot
2026-05-10 3:33 ` [PATCH 03/28] perf zstd: Fix compression error path in zstd_compress_stream_to_records() Arnaldo Carvalho de Melo
2026-05-12 0:13 ` sashiko-bot
2026-05-10 3:33 ` [PATCH 04/28] perf zstd: Fix multi-iteration decompression and error handling Arnaldo Carvalho de Melo
2026-05-10 3:33 ` [PATCH 05/28] perf session: Fix PERF_RECORD_READ swap and dump for variable-length events Arnaldo Carvalho de Melo
2026-05-10 3:33 ` [PATCH 06/28] perf session: Align auxtrace_info priv size before byte-swapping Arnaldo Carvalho de Melo
2026-05-10 3:33 ` [PATCH 07/28] perf session: Add validated swap infrastructure with null-termination checks Arnaldo Carvalho de Melo
2026-05-12 4:08 ` sashiko-bot
2026-05-10 3:33 ` [PATCH 08/28] perf session: Use bounded copy for PERF_RECORD_TIME_CONV Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 09/28] perf session: Validate HEADER_ATTR alignment and attr.size before swapping Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 10/28] perf session: Validate nr fields against event size on both swap and common paths Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 11/28] perf header: Byte-swap build ID event pid and bounds check section entries Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 12/28] perf cpumap: Reject RANGE_CPUS with start_cpu > end_cpu Arnaldo Carvalho de Melo
2026-05-12 21:37 ` sashiko-bot
2026-05-10 3:34 ` [PATCH 13/28] perf auxtrace: Harden auxtrace_error event handling Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 14/28] perf session: Add byte-swap and bounds check for PERF_RECORD_BPF_METADATA events Arnaldo Carvalho de Melo
2026-05-12 22:58 ` sashiko-bot
2026-05-10 3:34 ` [PATCH 15/28] perf header: Validate null-termination in PERF_RECORD_EVENT_UPDATE string fields Arnaldo Carvalho de Melo
2026-05-12 23:45 ` sashiko-bot
2026-05-10 3:34 ` [PATCH 16/28] perf tools: Bounds check perf_event_attr fields against attr.size before printing Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 17/28] perf header: Propagate feature section processing errors Arnaldo Carvalho de Melo
2026-05-13 3:21 ` sashiko-bot
2026-05-10 3:34 ` [PATCH 18/28] perf header: Validate f_attr.ids section before use in perf_session__read_header() Arnaldo Carvalho de Melo
2026-05-13 4:36 ` sashiko-bot
2026-05-10 3:34 ` [PATCH 19/28] perf header: Validate feature section size and add read path bounds checking Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 20/28] perf header: Sanity check HEADER_EVENT_DESC attr.size before swap Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 21/28] perf header: Validate bitmap size before allocating in do_read_bitmap() Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 22/28] perf session: Add byte-swap for PERF_RECORD_COMPRESSED2 events Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 23/28] perf tools: Harden compressed event processing Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 24/28] perf session: Check for decompression buffer size overflow Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 25/28] perf session: Bound nr_cpus_avail and validate sample CPU Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 26/28] perf timechart: Bounds check cpu_id and fix topology_map allocation Arnaldo Carvalho de Melo
2026-05-12 18:32 ` Ian Rogers
2026-05-12 19:48 ` Arnaldo Carvalho de Melo [this message]
2026-05-10 3:34 ` [PATCH 27/28] perf kwork: Bounds check work->cpu before indexing cpus_runtime[] Arnaldo Carvalho de Melo
2026-05-10 3:34 ` [PATCH 28/28] perf test: Add truncated perf.data robustness test Arnaldo Carvalho de Melo
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=agOECAaMwN_mQekU@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=noreply@anthropic.com \
--cc=sashiko-bot@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