linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Clark <james.clark@linaro.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>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	German Gomez <german.gomez@arm.com>,
	Ravi Bangoria <ravi.bangoria@amd.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Chun-Tse Shao <ctshao@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH v1 1/2] perf maps: Avoid RC_CHK use after free
Date: Wed, 19 Nov 2025 12:33:29 +0000	[thread overview]
Message-ID: <fe28fdc7-7c5c-420f-ac5c-903438d4d62b@linaro.org> (raw)
In-Reply-To: <20251119050555.2017758-1-irogers@google.com>



On 19/11/2025 5:05 am, Ian Rogers wrote:
> The case of __maps__fixup_overlap_and_insert where the "new" maps
> covers existing mappings can create a use-after-free with reference
> count checking enabled. The issue is that "pos" holds a map pointer
> from maps_by_address that is put from maps_by_address but then used to
> look for a map in maps_by_name (the compared map is now a
> use-after-free). The issue stems from using maps__remove which redoes
> some of the searches already done by __maps__fixup_overlap_and_insert,
> so optimize the code (by avoiding repeated searches) and avoid the
> use-after-free by inlining the appropriate removal code.
> 
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202511141407.f9edcfa6-lkp@intel.com
> Signed-off-by: Ian Rogers <irogers@google.com>

Reviewed-by: James Clark <james.clark@linaro.org>

> ---
>   tools/perf/util/maps.c | 22 ++++++++++++++++++++--
>   1 file changed, 20 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/util/maps.c b/tools/perf/util/maps.c
> index 779f6230130a..c321d4f4d846 100644
> --- a/tools/perf/util/maps.c
> +++ b/tools/perf/util/maps.c
> @@ -931,8 +931,9 @@ static int __maps__fixup_overlap_and_insert(struct maps *maps, struct map *new)
>   			return err;
>   		} else {
>   			struct map *next = NULL;
> +			unsigned int nr_maps = maps__nr_maps(maps);
>   
> -			if (i + 1 < maps__nr_maps(maps))
> +			if (i + 1 < nr_maps)
>   				next = maps_by_address[i + 1];
>   
>   			if (!next  || map__start(next) >= map__end(new)) {
> @@ -953,7 +954,24 @@ static int __maps__fixup_overlap_and_insert(struct maps *maps, struct map *new)
>   				check_invariants(maps);
>   				return err;
>   			}
> -			__maps__remove(maps, pos);
> +			/*
> +			 * pos fully covers the previous mapping so remove
> +			 * it. The following is an inlined version of
> +			 * maps__remove that reuses the already computed
> +			 * indices.
> +			 */
> +			map__put(maps_by_address[i]);
> +			memmove(&maps_by_address[i],
> +				&maps_by_address[i + 1],
> +				(nr_maps - i - 1) * sizeof(*maps_by_address));
> +
> +			if (maps_by_name) {
> +				map__put(maps_by_name[ni]);
> +				memmove(&maps_by_name[ni],
> +					&maps_by_name[ni + 1],
> +					(nr_maps - ni - 1) *  sizeof(*maps_by_name));
> +			}
> +			--RC_CHK_ACCESS(maps)->nr_maps;
>   			check_invariants(maps);
>   			/*
>   			 * Maps are ordered but no need to increase `i` as the


  parent reply	other threads:[~2025-11-19 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  5:05 [PATCH v1 1/2] perf maps: Avoid RC_CHK use after free Ian Rogers
2025-11-19  5:05 ` [PATCH v1 2/2] perf test maps: Additional maps__fixup_overlap_and_insert tests Ian Rogers
2025-11-19 12:33   ` James Clark
2025-11-19 12:33 ` James Clark [this message]
2025-11-20 19:02 ` [PATCH v1 1/2] perf maps: Avoid RC_CHK use after free 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=fe28fdc7-7c5c-420f-ac5c-903438d4d62b@linaro.org \
    --to=james.clark@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=ctshao@google.com \
    --cc=german.gomez@arm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.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;
as well as URLs for NNTP newsgroup(s).