public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Matt Brown <matt@nmatt.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
	jmorris@namei.org, gregkh@linuxfoundation.org, jslaby@suse.com,
	corbet@lwn.net, keescook@chromium.org, akpm@linux-foundation.org,
	jannh@google.com, kernel-hardening@lists.openwall.com,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 1/2] tiocsti-restrict : Add owner user namespace to tty_struct
Date: Sun, 23 Apr 2017 22:44:51 -0500	[thread overview]
Message-ID: <20170424034451.GA1620@mail.hallyn.com> (raw)
In-Reply-To: <7c4370cd-65ce-bc73-b93a-6825b7508f06@nmatt.com>

Quoting Matt Brown (matt@nmatt.com):
> On 04/23/2017 09:09 PM, Serge E. Hallyn wrote:
> >Quoting Matt Brown (matt@nmatt.com):
> >>This patch adds struct user_namespace *owner_user_ns to the tty_struct.
> >>Then it is set to current_user_ns() in the alloc_tty_struct function.
> >>
> >>This is done to facilitate capability checks against the original user
> >>namespace that allocated the tty.
> >>
> >>E.g. ns_capable(tty->owner_user_ns,CAP_SYS_ADMIN)
> >>
> >>This combined with the use of user namespace's will allow hardening
> >>protections to be built to mitigate container escapes that utilize TTY
> >>ioctls such as TIOCSTI.
> >>
> >>See: https://bugzilla.redhat.com/show_bug.cgi?id=1411256
> >>
> >>Signed-off-by: Matt Brown <matt@nmatt.com>
> >>---
> >> drivers/tty/tty_io.c | 4 ++++
> >> include/linux/tty.h  | 2 ++
> >> 2 files changed, 6 insertions(+)
> >>
> >>diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
> >>index e6d1a65..03d5ea2 100644
> >>--- a/drivers/tty/tty_io.c
> >>+++ b/drivers/tty/tty_io.c
> >>@@ -161,6 +161,7 @@ static void release_tty(struct tty_struct *tty, int idx);
> >>  *	@tty: tty struct to free
> >>  *
> >>  *	Free the write buffers, tty queue and tty memory itself.
> >>+ *	Decrement the owner_user_ns count.
> >>  *
> >>  *	Locking: none. Must be called after tty is definitely unused
> >>  */
> >>@@ -171,6 +172,7 @@ static void free_tty_struct(struct tty_struct *tty)
> >> 	put_device(tty->dev);
> >> 	kfree(tty->write_buf);
> >> 	tty->magic = 0xDEADDEAD;
> >>+	atomic_dec(&tty->owner_user_ns->count);
> >> 	kfree(tty);
> >> }
> >>
> >>@@ -3191,6 +3193,8 @@ struct tty_struct *alloc_tty_struct(struct tty_driver *driver, int idx)
> >> 	tty->index = idx;
> >> 	tty_line_name(driver, idx, tty->name);
> >> 	tty->dev = tty_get_device(tty);
> >>+	tty->owner_user_ns = current_user_ns();
> >>+	atomic_inc(&tty->owner_user_ns->count);
> >
> >Hi,
> >
> >CONFIG_USER_NS is an option, so unfortunately you need to do
> >
> >	tty->owner_user_ns = get_user_ns(current_user_ns());
> >
> 
> Does this mean I need to also use put_user_ns(tty->owner_user_ns) in
> free_tty_struct instead of atomic_dec(&tty->owner_user_ns->count) ?

Yes, and since in theory the tty could outlive all the tasks in the
user namespace it needs to be put_user_ns() anyway so as to free it
on last put.

  reply	other threads:[~2017-04-24  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 23:54 [PATCH v3 0/2] tiocsti-restrict : make TIOCSTI ioctl require CAP_SYS_ADMIN Matt Brown
2017-04-23 23:54 ` [PATCH v3 1/2] tiocsti-restrict : Add owner user namespace to tty_struct Matt Brown
2017-04-24  1:09   ` Serge E. Hallyn
2017-04-24  3:31     ` Matt Brown
2017-04-24  3:44       ` Serge E. Hallyn [this message]
2017-04-23 23:54 ` [PATCH v3 2/2] tiocsti-restrict : make TIOCSTI ioctl require CAP_SYS_ADMIN Matt Brown
2017-04-24  3:47   ` Serge E. Hallyn

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=20170424034451.GA1620@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=jmorris@namei.org \
    --cc=jslaby@suse.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=matt@nmatt.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