From: Suren Baghdasaryan <surenb@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Colin Cross <ccross@google.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Michal Hocko <mhocko@suse.com>,
Dave Hansen <dave.hansen@intel.com>,
Kees Cook <keescook@chromium.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
brauner@kernel.org, legion@kernel.org, ran.xiaokai@zte.com.cn,
sashal@kernel.org, Chris Hyser <chris.hyser@oracle.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Peter Collingbourne <pcc@google.com>,
caoxiaofeng@yulong.com, David Hildenbrand <david@redhat.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@android.com>,
syzbot+aa7b3d4b35f9dc46a366@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 1/1] mm: fix use-after-free when anon vma name is used after vma is freed
Date: Thu, 10 Feb 2022 07:21:52 -0800 [thread overview]
Message-ID: <CAJuCfpGhWh95wxRxy35d4jbCGUdCyasYQBs7DG2fVn34tSXrRQ@mail.gmail.com> (raw)
In-Reply-To: <YgUSxzp/qDwLkiKb@casper.infradead.org>
On Thu, Feb 10, 2022 at 5:27 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Feb 09, 2022 at 08:32:15PM -0800, Suren Baghdasaryan wrote:
> > +void vma_anon_name_put(struct anon_vma_name *anon_name)
> > +{
> > + kref_put(&anon_name->kref, vma_anon_name_free);
> > +}
>
> To agree with Michal, make this:
>
> if (anon_name)
> kref_put(&anon_name->kref, vma_anon_name_free);
Ack.
>
> >
> > - error = madvise_update_vma(vma, prev, start, end, new_flags,
> > - vma_anon_name(vma));
> > + anon_name = vma_anon_name_get(vma);
> > + if (anon_name) {
> > + error = madvise_update_vma(vma, prev, start, end, new_flags,
> > + anon_name->name);
> > + vma_anon_name_put(anon_name);
> > + } else {
> > + error = madvise_update_vma(vma, prev, start, end, new_flags,
> > + NULL);
> > + }
>
> And then this becomes:
>
> anon_name = vma_anon_name_get(vma);
> error = madvise_update_vma(vma, prev, start, end, new_flags, anon_name);
> vma_anon_name_put(anon_name);
As I indicated in the other reply, there is another madvise_update_vma
user which has only the name string, not the anon_vma_name struct. So
this can become:
anon_name = vma_anon_name_get(vma);
error = madvise_update_vma(vma, prev, start, end, new_flags,
anon_name ?
anon_name->name : NULL);
vma_anon_name_put(anon_name);
prev parent reply other threads:[~2022-02-10 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 4:32 [PATCH v2 1/1] mm: fix use-after-free when anon vma name is used after vma is freed Suren Baghdasaryan
2022-02-10 12:40 ` Michal Hocko
2022-02-10 15:18 ` Suren Baghdasaryan
2022-02-10 15:27 ` Matthew Wilcox
2022-02-10 16:00 ` Suren Baghdasaryan
2022-02-10 19:35 ` Matthew Wilcox
2022-02-10 19:52 ` Suren Baghdasaryan
2022-02-11 1:33 ` Suren Baghdasaryan
2022-02-10 13:27 ` Matthew Wilcox
2022-02-10 15:21 ` Suren Baghdasaryan [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=CAJuCfpGhWh95wxRxy35d4jbCGUdCyasYQBs7DG2fVn34tSXrRQ@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=caoxiaofeng@yulong.com \
--cc=ccross@google.com \
--cc=chris.hyser@oracle.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pcc@google.com \
--cc=ran.xiaokai@zte.com.cn \
--cc=sashal@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=syzbot+aa7b3d4b35f9dc46a366@syzkaller.appspotmail.com \
--cc=vbabka@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).