From: Luis Henriques <lhenriques@suse.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Sage Weil <sage@redhat.com>, Ilya Dryomov <idryomov@gmail.com>,
"Yan, Zheng" <ukernel@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ceph: Fix use-after-free in __ceph_remove_cap
Date: Mon, 28 Oct 2019 09:18:36 +0000 [thread overview]
Message-ID: <20191028091836.GA8558@hermes.olymp> (raw)
In-Reply-To: <1a9ac7d3097efe53ad6f2fda4dd584204dd7eba2.camel@kernel.org>
On Sun, Oct 27, 2019 at 08:31:49AM -0400, Jeff Layton wrote:
> On Fri, 2019-10-25 at 14:05 +0100, Luis Henriques wrote:
> > KASAN reports a use-after-free when running xfstest generic/531, with the
> > following trace:
> >
> > [ 293.903362] kasan_report+0xe/0x20
> > [ 293.903365] rb_erase+0x1f/0x790
> > [ 293.903370] __ceph_remove_cap+0x201/0x370
> > [ 293.903375] __ceph_remove_caps+0x4b/0x70
> > [ 293.903380] ceph_evict_inode+0x4e/0x360
> > [ 293.903386] evict+0x169/0x290
> > [ 293.903390] __dentry_kill+0x16f/0x250
> > [ 293.903394] dput+0x1c6/0x440
> > [ 293.903398] __fput+0x184/0x330
> > [ 293.903404] task_work_run+0xb9/0xe0
> > [ 293.903410] exit_to_usermode_loop+0xd3/0xe0
> > [ 293.903413] do_syscall_64+0x1a0/0x1c0
> > [ 293.903417] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> >
> > This happens because __ceph_remove_cap() may queue a cap release
> > (__ceph_queue_cap_release) which can be scheduled before that cap is
> > removed from the inode list with
> >
> > rb_erase(&cap->ci_node, &ci->i_caps);
> >
> > And, when this finally happens, the use-after-free will occur.
> >
> > This can be fixed by removing the cap from the inode list before being
> > removed from the session list, and thus eliminating the risk of an UAF.
> >
> > Signed-off-by: Luis Henriques <lhenriques@suse.com>
> > ---
> > Hi!
> >
> > So, after spending some time trying to find possible races throught code
> > review and testing, I modified the fix according to Jeff's suggestion.
> >
> > Cheers,
> > Luis
> >
> > fs/ceph/caps.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/fs/ceph/caps.c b/fs/ceph/caps.c
> > index d3b9c9d5c1bd..a9ce858c37d0 100644
> > --- a/fs/ceph/caps.c
> > +++ b/fs/ceph/caps.c
> > @@ -1058,6 +1058,11 @@ void __ceph_remove_cap(struct ceph_cap *cap, bool queue_release)
> >
> > dout("__ceph_remove_cap %p from %p\n", cap, &ci->vfs_inode);
> >
> > + /* remove from inode list */
> > + rb_erase(&cap->ci_node, &ci->i_caps);
> > + if (ci->i_auth_cap == cap)
> > + ci->i_auth_cap = NULL;
> > +
> > /* remove from session list */
> > spin_lock(&session->s_cap_lock);
> > if (session->s_cap_iterator == cap) {
> > @@ -1091,11 +1096,6 @@ void __ceph_remove_cap(struct ceph_cap *cap, bool queue_release)
> >
> > spin_unlock(&session->s_cap_lock);
> >
> > - /* remove from inode list */
> > - rb_erase(&cap->ci_node, &ci->i_caps);
> > - if (ci->i_auth_cap == cap)
> > - ci->i_auth_cap = NULL;
> > -
> > if (removed)
> > ceph_put_cap(mdsc, cap);
> >
>
> Looks good. Merged with a slight modification to the comment:
>
> + /* remove from inode's cap rbtree, and clear auth cap */
>
Awesome, thanks. Regarding CC: stable@, feel free to add that too. I
guess it makes sense, even if this issue has been there for a while
apparently without any reports. (Although UAFs may have non-obvious
side effects, I guess...)
Cheers,
--
Luís
> Thanks!
> --
> Jeff Layton <jlayton@kernel.org>
>
prev parent reply other threads:[~2019-10-28 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 14:46 [PATCH] ceph: Fix use-after-free in __ceph_remove_cap Luis Henriques
2019-10-21 12:38 ` Jeff Layton
2019-10-21 14:51 ` Luis Henriques
[not found] ` <CAAM7YA=dg8ufUWqrD_V8pSdvxrnU+knOW4uW4io_b=Lwjhpg5Q@mail.gmail.com>
2019-10-22 13:47 ` Luis Henriques
2019-10-23 10:29 ` Luis Henriques
2019-10-23 18:47 ` Jeff Layton
2019-10-25 13:05 ` [PATCH v2] " Luis Henriques
2019-10-27 12:31 ` Jeff Layton
2019-10-28 9:18 ` Luis Henriques [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=20191028091836.GA8558@hermes.olymp \
--to=lhenriques@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.com \
--cc=ukernel@gmail.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