From: Suren Baghdasaryan <surenb@google.com>
To: Jann Horn <jannh@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH 1/2] mm: lock_vma_under_rcu() must check vma->anon_vma under vma lock
Date: Thu, 27 Jul 2023 14:52:26 -0700 [thread overview]
Message-ID: <CAJuCfpHtE-2-NygxOJB+iaaEYuuLzqw3m=DLp0grQXwYPs5nLQ@mail.gmail.com> (raw)
In-Reply-To: <20230726214103.3261108-3-jannh@google.com>
On Wed, Jul 26, 2023 at 2:42 PM Jann Horn <jannh@google.com> wrote:
>
> lock_vma_under_rcu() tries to guarantee that __anon_vma_prepare() can't
> be called in the VMA-locked page fault path by ensuring that
> vma->anon_vma is set.
> However, this check happens before the VMA is locked, which means a
> concurrent move_vma() can concurrently call unlink_anon_vmas(), which
> disassociates the VMA's anon_vma.
>
> This means we can get UAF in the following scenario:
>
> THREAD 1 THREAD 2
> ======== ========
> <page fault>
> lock_vma_under_rcu()
> rcu_read_lock()
> mas_walk()
> check vma->anon_vma
>
> mremap() syscall
> move_vma()
> vma_start_write()
> unlink_anon_vmas()
> <syscall end>
>
> handle_mm_fault()
> __handle_mm_fault()
> handle_pte_fault()
> do_pte_missing()
> do_anonymous_page()
> anon_vma_prepare()
> __anon_vma_prepare()
> find_mergeable_anon_vma()
> mas_walk() [looks up VMA X]
>
> munmap() syscall (deletes VMA X)
>
> reusable_anon_vma() [called on freed VMA X]
>
> This is a security bug if you can hit it, although an attacker would
> have to win two races at once where the first race window is only a
> few instructions wide.
>
> This patch is based on some previous discussion with Linus Torvalds on
> the security list.
>
> Cc: stable@vger.kernel.org
> Fixes: 5e31275cc997 ("mm: add per-VMA lock and helper functions to control it")
> Signed-off-by: Jann Horn <jannh@google.com>
Reviewed-by: Suren Baghdasaryan <surenb@google.com>
> ---
> mm/memory.c | 28 ++++++++++++++++------------
> 1 file changed, 16 insertions(+), 12 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 01f39e8144ef..603b2f419948 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -5393,27 +5393,28 @@ struct vm_area_struct *lock_vma_under_rcu(struct mm_struct *mm,
> if (!vma_is_anonymous(vma) && !vma_is_tcp(vma))
> goto inval;
>
> - /* find_mergeable_anon_vma uses adjacent vmas which are not locked */
> - if (!vma->anon_vma && !vma_is_tcp(vma))
> - goto inval;
> -
> if (!vma_start_read(vma))
> goto inval;
>
> + /*
> + * find_mergeable_anon_vma uses adjacent vmas which are not locked.
> + * This check must happen after vma_start_read(); otherwise, a
> + * concurrent mremap() with MREMAP_DONTUNMAP could dissociate the VMA
> + * from its anon_vma.
> + */
> + if (unlikely(!vma->anon_vma && !vma_is_tcp(vma)))
> + goto inval_end_read;
> +
> /*
> * Due to the possibility of userfault handler dropping mmap_lock, avoid
> * it for now and fall back to page fault handling under mmap_lock.
> */
> - if (userfaultfd_armed(vma)) {
> - vma_end_read(vma);
> - goto inval;
> - }
> + if (userfaultfd_armed(vma))
> + goto inval_end_read;
>
> /* Check since vm_start/vm_end might change before we lock the VMA */
> - if (unlikely(address < vma->vm_start || address >= vma->vm_end)) {
> - vma_end_read(vma);
> - goto inval;
> - }
> + if (unlikely(address < vma->vm_start || address >= vma->vm_end))
> + goto inval_end_read;
>
> /* Check if the VMA got isolated after we found it */
> if (vma->detached) {
> @@ -5425,6 +5426,9 @@ struct vm_area_struct *lock_vma_under_rcu(struct mm_struct *mm,
>
> rcu_read_unlock();
> return vma;
> +
> +inval_end_read:
> + vma_end_read(vma);
> inval:
> rcu_read_unlock();
> count_vm_vma_lock_event(VMA_LOCK_ABORT);
> --
> 2.41.0.487.g6d72f3e995-goog
>
next prev parent reply other threads:[~2023-07-27 21:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 21:41 [PATCH 0/2] fix vma->anon_vma check for per-VMA locking; fix anon_vma memory ordering Jann Horn
2023-07-26 21:41 ` [PATCH 1/2] mm: lock_vma_under_rcu() must check vma->anon_vma under vma lock Jann Horn
2023-07-27 21:52 ` Suren Baghdasaryan [this message]
2023-07-26 21:41 ` [PATCH 2/2] mm: Fix anon_vma memory ordering Jann Horn
2023-07-26 21:50 ` Jann Horn
2023-07-27 18:25 ` Linus Torvalds
2023-07-26 23:19 ` [PATCH 0/2] fix vma->anon_vma check for per-VMA locking; fix " Paul E. McKenney
2023-07-27 14:39 ` Jann Horn
2023-07-27 14:57 ` Will Deacon
2023-07-27 15:44 ` Alan Stern
2023-07-27 16:10 ` Jann Horn
2023-07-27 16:17 ` Paul E. McKenney
2023-07-27 16:16 ` Paul E. McKenney
2023-07-27 17:11 ` Linus Torvalds
2023-07-27 17:41 ` Alan Stern
2023-07-27 18:01 ` Linus Torvalds
2023-07-27 19:05 ` Nadav Amit
2023-07-27 19:39 ` Linus Torvalds
2023-07-27 20:11 ` Nadav Amit
2023-07-28 9:18 ` Nadav Amit
2023-07-27 15:07 ` Matthew Wilcox
2023-07-27 15:15 ` Jann Horn
2023-07-27 16:09 ` Paul E. McKenney
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='CAJuCfpHtE-2-NygxOJB+iaaEYuuLzqw3m=DLp0grQXwYPs5nLQ@mail.gmail.com' \
--to=surenb@google.com \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linuxfoundation.org \
--cc=will@kernel.org \
--cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox