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>,
Stephane Eranian <eranian@google.com>,
Stefano Sanfilippo <ssanfilippo@chromium.org>
Subject: [PATCHES v2 0/12] perf jitdump: Input validation hardening
Date: Wed, 5 Aug 2026 18:26:50 -0300 [thread overview]
Message-ID: <20260805212704.267779-1-acme@kernel.org> (raw)
Hi,
Please consider merging,
This series addresses twelve classes of input validation and resource
handling bugs in the jitdump file format parser that could cause OOB
memory access or memory leaks when processing maliciously crafted or
corrupted jitdump files.
All issues were discovered by sashiko-bot during automated review of the
jitdump code path. The bugs affect both the native-endian and byte-swap
code paths, with some checks previously only enforced during
byte-swapping.
Critical fix:
code_size validation was bypassable via int truncation. A record with
code_size in [2^31, record_size - 56] passed the existing bounds check
in jit_repipe_code_load() but truncated to a negative int when sent to
jit_process_code_load(), so the code pointer landed ~2GiB past the
record buffer, defeating the memchr() NUL scan and corrupting the
injected ELF.
Before: code_size = 0x80000010 passes the range check, then truncates
to a negative offset
After: code_size > INT_MAX is rejected up front; all subsequent code
size arithmetic stays within the record buffer
Best regards,
- Arnaldo
Changes since v1 (20260805133013.235016-1-acme@kernel.org):
- Rebased onto the current perf-tools-next head (fe3ab00d55aa56b4).
- All 12 patches now carry a Reviewed-by: Ian Rogers <irogers@google.com>.
- Applied the code-convention suggestions from Ian's review of v1:
- Patch "perf jitdump: Check snprintf return before computing header
size": the clamp now uses sizeof(event->mmap2.filename) instead of
PATH_MAX in both jit_repipe_code_load() and
jit_repipe_code_move(), tying the bound to the actual destination
buffer.
- Patch "perf jitdump: Use dirname() return value in jit_open()":
the strlcpy() bound uses sizeof(jd->dir) instead of PATH_MAX.
- A cosmetics-only remark about the include order of <limits.h> was
deliberately not applied.
Issues fixed:
Validation and bounds checks:
- Validate code_size against both the record size and INT_MAX in
jit_repipe_code_load()
- Prevent integer underflow in the debug info size calculation
- Bounds-check the debug entry byte-swap loop
- Validate debug entries on the native (non-swap) path, matching the
existing byte-swap path checks
- Validate sym string NUL-termination in code load, bounding the
strlen() scan to the code blob
- Validate unwinding sizes against the record payload before allocating
- Check the snprintf() return before computing the header size, and
clamp against the actual buffer size
Stream and record handling:
- Fix the extended header read that always failed, causing records to
be misparsed
- Use dirname()'s return value in jit_open(), fixing ENOTDIR failures
- Fix funlockfile() being called on an unlocked stream in the jit_open()
error path
Resource management:
- Free the event in jit_repipe_code_move()
- Fix debug_data and unwinding_data leaks when records are overwritten
Each patch includes a Fixes: tag pointing to the offending commit, dating
back to jitdump mmap injection support (9b07e27f88b9cd78), source line
info support (598b7c6919c7bbcc), and unwinding support
(0284fecd13b6db3e), all from the original 2016 jitdump work.
Testing: Built and tested on x86_64. No existing tests cover jitdump
parsing with malformed input; test suite expansion is left for future
work. The final series was re-reviewed after the fixes and the v1
review (build-checked, Fixes: tags verified); no regressions found.
AI assistance: This series was developed with assistance from Claude
(claude-opus-4.6) and Opencode (deepseek-v4-flash-free) for code
analysis, patch generation, and commit message composition.
Arnaldo Carvalho de Melo (12):
perf jitdump: Fix extended header read that always fails
perf jitdump: Validate code_size against total_size in code load
perf jitdump: Prevent integer underflow in debug info size calculation
perf jitdump: Bounds-check debug entry byte-swap loop
perf jitdump: Check snprintf return before computing header size
perf jitdump: Fix funlockfile on unlocked stream in jit_open() error path
perf jitdump: Free event in jit_repipe_code_move()
perf jitdump: Fix debug_data and unwinding_data leaks
perf jitdump: Use dirname() return value in jit_open()
perf jitdump: Validate debug entries on native (non-swap) path
perf jitdump: Validate sym string NUL-termination in code load
perf jitdump: Validate unwinding sizes against record payload
tools/perf/util/jitdump.c | 126 +++++++++++++++++++++++++++++++++++++++-------
1 file changed, 108 insertions(+), 18 deletions(-)
base-commit: fe3ab00d55aa56b4d55cbc1150448f0aadd6732c
Arnaldo Carvalho de Melo (12):
perf jitdump: Fix extended header read that always fails
perf jitdump: Validate code_size against total_size in code load
perf jitdump: Prevent integer underflow in debug info size calculation
perf jitdump: Bounds-check debug entry byte-swap loop
perf jitdump: Check snprintf return before computing header size
perf jitdump: Fix funlockfile on unlocked stream in jit_open() error
path
perf jitdump: Free event in jit_repipe_code_move()
perf jitdump: Fix debug_data and unwinding_data leaks
perf jitdump: Use dirname() return value in jit_open()
perf jitdump: Validate debug entries on native (non-swap) path
perf jitdump: Validate sym string NUL-termination in code load
perf jitdump: Validate unwinding sizes against record payload
tools/perf/util/jitdump.c | 126 ++++++++++++++++++++++++++++++++------
1 file changed, 108 insertions(+), 18 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-05 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 21:26 Arnaldo Carvalho de Melo [this message]
2026-08-05 21:26 ` [PATCH 01/12] perf jitdump: Fix extended header read that always fails Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 02/12] perf jitdump: Validate code_size against total_size in code load Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 03/12] perf jitdump: Prevent integer underflow in debug info size calculation Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 04/12] perf jitdump: Bounds-check debug entry byte-swap loop Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 05/12] perf jitdump: Check snprintf return before computing header size Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 06/12] perf jitdump: Fix funlockfile on unlocked stream in jit_open() error path Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 07/12] perf jitdump: Free event in jit_repipe_code_move() Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 08/12] perf jitdump: Fix debug_data and unwinding_data leaks Arnaldo Carvalho de Melo
2026-08-05 21:26 ` [PATCH 09/12] perf jitdump: Use dirname() return value in jit_open() Arnaldo Carvalho de Melo
2026-08-05 21:27 ` [PATCH 10/12] perf jitdump: Validate debug entries on native (non-swap) path Arnaldo Carvalho de Melo
2026-08-05 21:27 ` [PATCH 11/12] perf jitdump: Validate sym string NUL-termination in code load Arnaldo Carvalho de Melo
2026-08-05 21:27 ` [PATCH 12/12] perf jitdump: Validate unwinding sizes against record payload 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=20260805212704.267779-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=eranian@google.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=ssanfilippo@chromium.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