public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Pavel Emelyanov <xemul@openvz.org>,
	Daniel Lezcano <dlezcano@fr.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] devices cgroup: allow mkfifo
Date: Thu, 11 Dec 2008 08:59:57 -0600	[thread overview]
Message-ID: <20081211145956.GB10107@us.ibm.com> (raw)
In-Reply-To: <49406553.6000408@cn.fujitsu.com>

Quoting Li Zefan (lizf@cn.fujitsu.com):
> CC: Andrew
> 
> Serge E. Hallyn wrote:
> > The devcgroup_inode_permission() hook in the devices whitelist
> > cgroup has always bypassed access checks on fifos.  But the
> > mknod hook did not.  The devices whitelist is only about block
> > and char devices, and fifos can't even be added to the whitelist,
> > so fifos can't be created at all except by tasks which have 'a'
> > in their whitelist (meaning they have access to all devices).
> > 
> > Fix the behavior by bypassing access checks to mkfifo.
> > 
> 
> It also bypasses checks to mksock. Should backport this patch?

Do you mean push it into -stable?

Couldn't hurt, but it's a DOS to root in a container, not a security
vulnerability, and since noone has complainted until now so at least
it's not panick-worthy.

> Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>

Thanks.  I'll go ahead and send to Linus and -stable.

-serge

> > Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
> > ---
> >  security/device_cgroup.c |    3 +++
> >  1 files changed, 3 insertions(+), 0 deletions(-)
> > 
> > diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> > index 5ba7870..df9d491 100644
> > --- a/security/device_cgroup.c
> > +++ b/security/device_cgroup.c
> > @@ -513,6 +513,9 @@ int devcgroup_inode_mknod(int mode, dev_t dev)
> >  	struct dev_cgroup *dev_cgroup;
> >  	struct dev_whitelist_item *wh;
> >  
> > +	if (!S_ISBLK(mode) && !S_ISCHR(mode))
> > +		return 0;
> > +
> >  	rcu_read_lock();
> >  
> >  	dev_cgroup = task_devcgroup(current);

  reply	other threads:[~2008-12-11 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 15:57 [PATCH 1/1] devices cgroup: allow mkfifo Serge E. Hallyn
2008-12-11  0:56 ` Li Zefan
2008-12-11 14:59   ` Serge E. Hallyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-11 15:50 Serge E. Hallyn
2008-12-12  3:12 ` Andrew Morton
2008-12-12 14:34   ` Serge E. Hallyn
2008-12-13  7:09     ` Li Zefan

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=20081211145956.GB10107@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=xemul@openvz.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