From: "J. Bruce Fields" <bfields@fieldses.org>
To: Meng Xu <mengxu.gatech@gmail.com>
Cc: jlayton@poochiereds.net, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org, meng.xu@gatech.edu,
sanidhya@gatech.edu, taesoo@gatech.edu
Subject: Re: [PATCH] nfsd4: ensure cm_xid does not change across userspace fetches
Date: Wed, 27 Sep 2017 17:06:50 -0400 [thread overview]
Message-ID: <20170927210650.GA16674@fieldses.org> (raw)
In-Reply-To: <20170926215216.GA30989@fieldses.org>
On Tue, Sep 26, 2017 at 05:52:16PM -0400, J. Bruce Fields wrote:
> On Sun, Sep 24, 2017 at 12:59:40PM -0400, Meng Xu wrote:
> > cld_pipe_downcall() has two fetches from an overapped userspace memory.
> > The first fetch copy_from_user(&xid, &cmsg->cm_xid, sizeof(xid)) get
> > the xid and use xid to lookup the parent struct cld_upcall *cup.
> > The second fetch copy_from_user(&cup->cu_msg, src, mlen) place the whole
> > message into &cup->cu_msg.
> >
> > Since the userspace thread has full control over this &cmsg->cm_xid,
> > it can race condition to change the cm_xid value across the two fetches,
> > (say, change from 1 to 2), therefore, de-listing the cup with
> > cu_msg.cm_xid == 1 but later put cu_msg.cm_xid = 2.
> >
> > Whether this double-fetch situation is a security critical bug depends
> > on how cup->cu_msg is used later. However, given that it is hard to
> > enumerate all the possible use cases, a safer way might be to ensure
> > that the xid does not change across the fetches, which is what this
> > patch is for.
>
> Alternatively, couldn't we copy the whole message just once at the
> start? It doesn't look like there very large, so there's room for it on
> the stack, if that's the problem.
Well, I'm bikeshedding, your version's OK.
I'm not convinced there's really a bug, though: as far as I can tell we
*only* use the xid for matching call and response, so if it's changed it
doesn't affect what any later code does.
--b.
>
> --b.
>
> >
> > Signed-off-by: Meng Xu <mengxu.gatech@gmail.com>
> > ---
> > fs/nfsd/nfs4recover.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/fs/nfsd/nfs4recover.c b/fs/nfsd/nfs4recover.c
> > index 66eaeb1..1abe9ed 100644
> > --- a/fs/nfsd/nfs4recover.c
> > +++ b/fs/nfsd/nfs4recover.c
> > @@ -753,6 +753,11 @@ cld_pipe_downcall(struct file *filp, const char __user *src, size_t mlen)
> > if (copy_from_user(&cup->cu_msg, src, mlen) != 0)
> > return -EFAULT;
> >
> > + /* ensure that the xid has not been changed */
> > + if (cup->cu_msg.cm_xid != xid) {
> > + return -EFAULT;
> > + }
> > +
> > wake_up_process(cup->cu_task);
> > return mlen;
> > }
> > --
> > 2.7.4
prev parent reply other threads:[~2017-09-27 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 16:59 [PATCH] nfsd4: ensure cm_xid does not change across userspace fetches Meng Xu
2017-09-26 21:52 ` J. Bruce Fields
2017-09-27 21:06 ` J. Bruce Fields [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=20170927210650.GA16674@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=meng.xu@gatech.edu \
--cc=mengxu.gatech@gmail.com \
--cc=sanidhya@gatech.edu \
--cc=taesoo@gatech.edu \
/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).