All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Athira Rajeev <atrajeev@linux.ibm.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf disasm: Fix potential use-after-free on fileloc
Date: Wed, 11 Mar 2026 18:17:58 -0700	[thread overview]
Message-ID: <abIURgnW94VGFo8k@google.com> (raw)
In-Reply-To: <20260307002222.2463509-1-irogers@google.com>

On Fri, Mar 06, 2026 at 04:22:22PM -0800, Ian Rogers wrote:
> The fileloc is a copy of a pointer to a string but in places like
> symbol_disassemble__llvm this string appears to be freed setting up
> potential use-after-frees:
> 
> llvm.c:
> ```
> 		dl = disasm_line__new(args);
> 		if (dl == NULL)
> 			goto err;
> 
> 		annotation_line__add(&dl->al, &notes->src->source);
> 
> 		free(args->fileloc);
> ```
> disasm.c:
> ```
> static void annotation_line__init(struct annotation_line *al,
> 				  struct annotate_args *args,
> 				  int nr)
> {
> 	al->offset = args->offset;
> 	al->line = strdup(args->line);
> 	al->line_nr = args->line_nr;
> 	al->fileloc = args->fileloc;
> 	al->data_nr = nr;
> }
> 
> struct disasm_line *disasm_line__new(struct annotate_args *args)
> {
> 	struct disasm_line *dl = NULL;
> 	struct annotation *notes = symbol__annotation(args->ms->sym);
> 	int nr = notes->src->nr_events;
> 
> 	dl = zalloc(disasm_line_size(nr));
> 	if (!dl)
> 		return NULL;
> 
> 	annotation_line__init(&dl->al, args, nr);
> ```
> 
> Fix this by making the fileloc a copy of the underlying string in its
> init/exit.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>

Applied to perf-tools-next, thanks!

Best regards,
Namhyung


      reply	other threads:[~2026-03-12  1:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  0:22 [PATCH v2] perf disasm: Fix potential use-after-free on fileloc Ian Rogers
2026-03-12  1:17 ` Namhyung Kim [this message]

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=abIURgnW94VGFo8k@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@linux.ibm.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@redhat.com \
    --cc=peterz@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.