From: Jens Axboe <axboe@kernel.dk>
To: Filippo Sironi <sironi@amazon.de>, linux-kernel@vger.kernel.org
Cc: dwmw@amazon.co.uk, christian.brauner@ubuntu.com,
akpm@linux-foundation.org, ebiederm@xmission.com,
peterz@infradead.org, keescook@chromium.org,
krisman@collabora.com, peterx@redhat.com, surenb@google.com,
shakeelb@google.com, guro@fb.com, elver@google.com
Subject: Re: [RFC PATCH] mm: fork: Prevent a NULL deref by getting mm only if the refcount isn't 0
Date: Wed, 10 Mar 2021 08:57:00 -0700 [thread overview]
Message-ID: <4130ef8d-7b97-f63d-00fc-0ee2b494e1d0@kernel.dk> (raw)
In-Reply-To: <20210310123703.27894-1-sironi@amazon.de>
On 3/10/21 5:37 AM, Filippo Sironi wrote:
> We've seen a number of crashes with the following signature:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> ...
> Oops: 0000 [#1] SMP PTI
> ...
> RIP: 0010:__rb_erase_color+0xc2/0x260
> ...
> Call Trace:
> unlink_file_vma+0x36/0x50
> free_pgtables+0x62/0x110
> exit_mmap+0xd5/0x160
> ? put_dec+0x3a/0x90
> ? num_to_str+0xa8/0xc0
> mmput+0x11/0xb0
> do_task_stat+0x940/0xc80
> proc_single_show+0x49/0x80
> ? __check_object_size+0xcc/0x1a0
> seq_read+0xd3/0x400
> vfs_read+0x72/0xb0
> ksys_read+0x9c/0xd0
> do_syscall_64+0x69/0x400
> ? schedule+0x2a/0x90
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> ...
>
> This happens when a process goes through the tasks stats in procfs while
> another is exiting. This looks like a race where the process that's
> exiting drops the last reference on the mm (with mmput) while the other
> increases it (with mmget). By only increasing when the reference isn't
> 0 to begin with, we prevent this from happening.
From a quick look it looks reasonable, but I don't quite see how we get
in the situation of finding a valid ->mm under task_lock() and the
mm_users count being 0? I'd like to understand that, because it may just
be that your patch just narrows the gap but it's still possible to
trigger a use-after-free. Doesn't seem like that would be possible under
exit_mm().
--
Jens Axboe
next prev parent reply other threads:[~2021-03-10 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 12:37 [RFC PATCH] mm: fork: Prevent a NULL deref by getting mm only if the refcount isn't 0 Filippo Sironi
2021-03-10 15:57 ` Jens Axboe [this message]
2021-03-10 17:09 ` Eric W. Biederman
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=4130ef8d-7b97-f63d-00fc-0ee2b494e1d0@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=dwmw@amazon.co.uk \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=guro@fb.com \
--cc=keescook@chromium.org \
--cc=krisman@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=shakeelb@google.com \
--cc=sironi@amazon.de \
--cc=surenb@google.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