From: Ian Kent <raven@themaw.net>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: [PATCH] autofs4: check dev ioctl size before allocating
Date: Sun, 06 Apr 2014 11:03:23 +0800 [thread overview]
Message-ID: <1396753403.24991.3.camel@perseus.fritz.box> (raw)
In-Reply-To: <53401C11.7010601@oracle.com>
On Sat, 2014-04-05 at 11:06 -0400, Sasha Levin wrote:
> Ping? Anyone wants to take this?
Is this causing a problem for users?
If it is I'll send it to Andrew straight away.
I do have this on my queue but don't have any other patches to send so
it's just sitting there.
If it worries you I'll send it to Andrew now.
>
> On 03/15/2014 09:40 PM, Sasha Levin wrote:
> > There wasn't any check of the size passed from userspace before
> > trying to allocate the memory required.
> >
> > This meant that userspace might request more space than allowed,
> > triggering an OOM.
> >
> > Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> > ---
> > fs/autofs4/dev-ioctl.c | 3 +++
> > 1 files changed, 3 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/autofs4/dev-ioctl.c b/fs/autofs4/dev-ioctl.c
> > index 3182c0e..86fa7af 100644
> > --- a/fs/autofs4/dev-ioctl.c
> > +++ b/fs/autofs4/dev-ioctl.c
> > @@ -103,6 +103,9 @@ static struct autofs_dev_ioctl *copy_dev_ioctl(struct autofs_dev_ioctl __user *i
> > if (tmp.size < sizeof(tmp))
> > return ERR_PTR(-EINVAL);
> >
> > + if (tmp.size > (PATH_MAX + sizeof(tmp)))
> > + return ERR_PTR(-E2BIG);
> > +
> > return memdup_user(in, tmp.size);
> > }
> >
> >
>
next prev parent reply other threads:[~2014-04-06 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1394934021-16965-1-git-send-email-sasha.levin@oracle.com>
2014-04-05 15:06 ` [PATCH] autofs4: check dev ioctl size before allocating Sasha Levin
2014-04-06 3:03 ` Ian Kent [this message]
2014-04-06 3:11 ` Sasha Levin
2014-04-06 3:53 ` Ian Kent
2014-04-07 0:03 ` Sasha Levin
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=1396753403.24991.3.camel@perseus.fritz.box \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=viro@ZenIV.linux.org.uk \
/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).