From: Peter Zijlstra <peterz@infradead.org>
To: Chengming Zhou <zhouchengming@bytedance.com>
Cc: syzbot <syzbot+b8e8c01c8ade4fe6e48f@syzkaller.appspotmail.com>,
acme@kernel.org, alexander.shishkin@linux.intel.com,
bpf@vger.kernel.org, jolsa@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in put_pmu_ctx
Date: Thu, 22 Dec 2022 21:59:21 +0100 [thread overview]
Message-ID: <Y6TFKdVJ9BY56fkI@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <3a5a4738-2868-8f2f-f8b2-a28c10fbe25b@linux.dev>
On Wed, Dec 21, 2022 at 10:42:39AM +0800, Chengming Zhou wrote:
> > Does this help?
> >
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index e47914ac8732..bbff551783e1 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -12689,7 +12689,8 @@ SYSCALL_DEFINE5(perf_event_open,
> > return event_fd;
> >
> > err_context:
> > - /* event->pmu_ctx freed by free_event() */
> > + put_pmu_ctx(event->pmu_ctx);
> > + event->pmu_ctx = NULL; /* _free_event() */
> > err_locked:
> > mutex_unlock(&ctx->mutex);
> > perf_unpin_context(ctx);
>
> Tested-by: Chengming Zhou <zhouchengming@bytedance.com>
>
> While reviewing the code, I found perf_event_create_kernel_counter()
> has the similar problem in the "err_pmu_ctx" error handling path:
Right you are, updated the patch, thanks!
> CPU0 CPU1
> perf_event_create_kernel_counter()
> // inc ctx refcnt
> find_get_context(task, event) (1)
>
> // inc pmu_ctx refcnt
> pmu_ctx = find_get_pmu_context()
>
> event->pmu_ctx = pmu_ctx
> ...
> goto err_pmu_ctx:
> // dec pmu_ctx refcnt
> put_pmu_ctx(pmu_ctx) (2)
>
> mutex_unlock(&ctx->mutex)
> // dec ctx refcnt
> put_ctx(ctx)
> perf_event_exit_task_context()
> mutex_lock()
> mutex_unlock()
> // last refcnt put
> put_ctx()
> free_event(event)
> if (event->pmu_ctx) // True
> put_pmu_ctx() (3)
> // will access freed pmu_ctx or ctx
>
> if (event->ctx) // False
> put_ctx()
This doesn't look right; iirc you can hit this without concurrency,
something like so:
// note that when getting here, we've not passed
// perf_install_in_context() and event->ctx == NULL.
err_pmu_ctx:
put_pmu_ctx();
put_ctx(); // last, actually frees ctx
..
err_alloc:
free_event()
_free_event()
if (event->pmu_ctx) // true, because we forgot to clear
put_pmu_ctx() // hits 0 because double put
// goes and touch epc->ctx and UaF
next prev parent reply other threads:[~2022-12-22 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 8:04 [syzbot] KASAN: use-after-free Read in put_pmu_ctx syzbot
2022-12-19 14:40 ` Peter Zijlstra
2022-12-19 19:33 ` sdf
2022-12-19 19:56 ` syzbot
2022-12-19 21:33 ` sdf
2022-12-19 22:24 ` syzbot
2022-12-20 8:22 ` Peter Zijlstra
2022-12-20 17:10 ` Stanislav Fomichev
2022-12-20 19:37 ` syzbot
2022-12-21 2:42 ` Chengming Zhou
2022-12-22 20:59 ` Peter Zijlstra [this message]
2022-12-23 10:08 ` Chengming Zhou
2022-12-20 8:25 ` Peter Zijlstra
2022-12-20 8:43 ` syzbot
2022-12-20 10:04 ` Peter Zijlstra
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=Y6TFKdVJ9BY56fkI@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.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=netdev@vger.kernel.org \
--cc=syzbot+b8e8c01c8ade4fe6e48f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zhouchengming@bytedance.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).