From: SeongJae Park <sj@kernel.org>
To: Stanislav Fort <stanislav.fort@aisle.com>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Stanislav Fort <disclosure@aisle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] mm/damon/sysfs: fix use-after-free in state_show()
Date: Fri, 5 Sep 2025 13:12:50 -0700 [thread overview]
Message-ID: <20250905201250.36561-1-sj@kernel.org> (raw)
In-Reply-To: <20250905101046.2288-1-disclosure@aisle.com>
+ Andrew
On Fri, 5 Sep 2025 13:10:46 +0300 Stanislav Fort <stanislav.fort@aisle.com> wrote:
> state_show() reads kdamond->damon_ctx without holding damon_sysfs_lock.
> This allows a use-after-free race:
>
> CPU 0 CPU 1
> ----- -----
> state_show() damon_sysfs_turn_damon_on()
> ctx = kdamond->damon_ctx; mutex_lock(&damon_sysfs_lock);
> damon_destroy_ctx(kdamond->damon_ctx);
> kdamond->damon_ctx = NULL;
> mutex_unlock(&damon_sysfs_lock);
> damon_is_running(ctx); /* ctx is freed */
> mutex_lock(&ctx->kdamond_lock); /* UAF */
>
> (The race can also occur with damon_sysfs_kdamonds_rm_dirs() and
> damon_sysfs_kdamond_release(), which free or replace the context under
> damon_sysfs_lock.)
>
> Fix by taking damon_sysfs_lock before dereferencing the context,
> mirroring the locking used in pid_show().
>
> The bug has existed since state_show() first accessed kdamond->damon_ctx.
>
> Fixes: a61ea561c871 ("mm/damon/sysfs: link DAMON for virtual address spaces monitoring")
> Reported-by: Stanislav Fort <disclosure@aisle.com>
> Closes: N/A # non-publicly reported
> Signed-off-by: Stanislav Fort <disclosure@aisle.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-09-05 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 10:10 Stanislav Fort
2025-09-05 20:12 ` SeongJae Park [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=20250905201250.36561-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=disclosure@aisle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stanislav.fort@aisle.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