From: Aaron Tomlin <atomlin@atomlin.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org
Cc: mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, howardchu95@gmail.com,
atomlin@atomlin.com, neelx@suse.com, chjohnst@mail.com,
sean@ashe.io, steve@abita.co, rishil1999@outlook.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 perf-tools-next 0/6] perf trace: Validate payload bounds across augmented argument beautifiers
Date: Sun, 6 Sep 2026 21:51:34 -0400 [thread overview]
Message-ID: <20260907015140.363076-1-atomlin@atomlin.com> (raw)
When pretty-printing augmented syscall arguments in perf trace, raw payload
data captured from BPF programs is passed to various argument formatters
via struct syscall_arg.
However, when processing malformed, truncated, or untrusted perf.data
records (e.g., truncated reads in BPF ringbuffers, cross-architecture
replays, or crafted sample records), the payload can be shorter than
expected or contain invalid size fields:
1. Dereferencing augmented_arg fields before validating that
arg->augmented.size is at least sizeof(struct augmented_arg) can read
past the available buffer.
2. Passing augmented_arg->size to formatters or loop counters without
bounding it against the remaining buffer can cause out-of-bounds memory
reads.
3. In multi-argument syscalls, calculating consumed bytes as:
consumed = sizeof(*augmented_arg) + augmented_arg->size;
without bounds checking can overflow signed integer bounds or cause
arg->augmented.size to underflow. This advances arg->augmented.args
out of bounds, corrupting parsing state for all subsequent
arguments in the same syscall.
4. Type/family-specific beautifiers (i.e., BTF struct dump, sockaddr,
timespec, perf_event_attr) can dereference structure fields without
verifying that the payload contains sufficient bytes for the target
type.
This series adds comprehensive upper-bound and payload-size checks across
all augmented argument beautifiers in perf trace. If validation fails in
any beautifier, it cleanly falls back to printing the raw pointer/hex
value.
To facilitate clean, conflict-free backports across active LTS kernels,
each formatter fix is isolated to its own commit.
Changes since v1:
- Expanded the original single patch into a 6-patch series in response to
reviewer feedback from sashiko-bot regarding similar bounds check
omissions across other augmented formatters in perf trace
- Added new patch validating payload bounds and consumed offset
calculations in syscall_arg__scnprintf_augmented_string()
- Added new patch validating payload bounds before byte traversal in
syscall_arg__scnprintf_buf(), isolated to ensure an independent Fixes:
tag for stable backports
- Added new patch validating payload size against sizeof(struct timespec)
in syscall_arg__scnprintf_augmented_timespec()
- Added new patch validating payload bounds and family-specific lengths in
syscall_arg__scnprintf_augmented_sockaddr()
- Added new patch validating payload size against at least
PERF_ATTR_SIZE_VER0 in
syscall_arg__scnprintf_augmented_perf_event_attr()
- Link to v1: https://lore.kernel.org/all/20260906011132.279321-1-atomlin@atomlin.com/
Aaron Tomlin (6):
perf trace: Add upper bound checks for augmented BTF struct printing
perf trace: Validate payload bounds in augmented string beautifier
perf trace: Validate payload bounds in augmented buffer beautifier
perf trace beauty: Validate payload size in augmented timespec
beautifier
perf trace beauty: Validate payload size in augmented sockaddr
beautifier
perf trace beauty: Validate payload size in augmented perf_event_open
beautifier
tools/perf/builtin-trace.c | 36 +++++++++++++++++------
tools/perf/trace/beauty/perf_event_open.c | 19 ++++++++++--
tools/perf/trace/beauty/sockaddr.c | 35 ++++++++++++++++++----
tools/perf/trace/beauty/timespec.c | 19 ++++++++++--
4 files changed, 89 insertions(+), 20 deletions(-)
base-commit: 02f6847e1822714a4201b87e42f92b0d43e8549d
--
2.55.0
next reply other threads:[~2026-09-07 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 1:51 Aaron Tomlin [this message]
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 1/6] perf trace: Add upper bound checks for augmented BTF struct printing Aaron Tomlin
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 2/6] perf trace: Validate payload bounds in augmented string beautifier Aaron Tomlin
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 3/6] perf trace: Validate payload bounds in augmented buffer beautifier Aaron Tomlin
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 4/6] perf trace beauty: Validate payload size in augmented timespec beautifier Aaron Tomlin
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 5/6] perf trace beauty: Validate payload size in augmented sockaddr beautifier Aaron Tomlin
2026-09-07 1:51 ` [PATCH v2 perf-tools-next 6/6] perf trace beauty: Validate payload size in augmented perf_event_open beautifier Aaron Tomlin
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=20260907015140.363076-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=chjohnst@mail.com \
--cc=howardchu95@gmail.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=neelx@suse.com \
--cc=peterz@infradead.org \
--cc=rishil1999@outlook.com \
--cc=sean@ashe.io \
--cc=steve@abita.co \
/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
all inboxes | Powered by JetHome®