From: Serge Hallyn <serge@hallyn.com>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com, akpm@linux-foundation.org,
oleg@redhat.com, richard@nod.at, mikevs@xs4all.net,
segoon@openwall.com, gregkh@suse.de, dhowells@redhat.com,
eparis@redhat.com
Subject: user namespaces: fix some uid/privilege leaks
Date: Tue, 18 Oct 2011 21:54:49 +0000 [thread overview]
Message-ID: <1318974898-21431-1-git-send-email-serge@hallyn.com> (raw)
The set of patches which I'm currently aiming to get upstream is queued at:
http://kernel.ubuntu.com/git?p=serge/linux-2.6.git;a=shortlog;h=refs/heads/userns
In the below descriptions, it helps to remember that a task can have more
privilege to his own, child, user namespace, than he does in his parent or
the initial user namespace. In fact a task created in a new user namespace
receives all capabilities (within bounding set) in the new user namespace.
So checks for privilege in a task's own user ns can not be safely used in place
of checks against another user ns.
The set includes:
0001-pid_ns-ensure-pid-is-not-freed-during-kill_pid_info_.patch
Fix a case where a pid could be referenced after being freed.
(This is in Greg's usb tree, but not yet in Linus' tree; it's
here just to show full context)
0002-user-namespace-usb-make-usb-urbs-user-namespace-awar.patch
Take the user namespace into account when comparing uids when
signals are sent by usb urbs.
(This is in Greg's usb tree, but not yet in Linus' tree; it's
here just to show full context)
0003-user-namespace-make-signal.c-respect-user-namespaces.patch
This convers the uid for the task sending a signal to the
user namespace of the receiver. It is somewhat analogous
to what is done with the sender's pid.
Waiting on feedback from Oleg, but I believe this patch is
ready.
0004-User-namespace-don-t-allow-sysctl-in-non-init-user-n.patch
This prevents root in a child user namespace from man-handling
sysctls. With this patch, a task in a child user namespace
will only get the world access rights to sysctls.
0005-user-namespace-clamp-down-users-of-cap_raised.patch
This clamps down on cases where privilege to your own user
namespace were checked for access to the initial user namespace.
0006-Add-Documentation-namespaces-user_namespace.txt-v3.patch
Documentation.
0007-user-namespace-make-each-net-net_ns-belong-to-a-user.patch
This adds a struct user_namespace pointer to the net_ns for use
by later patches.
0008-protect-cap_netlink_recv-from-user-namespaces.patch
Now that net_ns is owned by a user_ns, cap_netlink_recv() can
target privilege checks to the user_ns owning the resource. The
current check against current_cap() is unsafe.
0009-make-net-core-scm.c-uid-comparisons-user-namespace-a.patch
In scm_send, uids of sender/receiver are being compared without
accounting for different user namespaces. Fix that.
next reply other threads:[~2011-10-18 21:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 21:54 Serge Hallyn [this message]
2011-10-18 21:54 ` [PATCH 1/9] pid_ns: ensure pid is not freed during kill_pid_info_as_uid Serge Hallyn
2011-10-18 21:54 ` [PATCH 2/9] user namespace: usb: make usb urbs user namespace aware (v2) Serge Hallyn
2011-10-18 21:54 ` [PATCH 3/9] user namespace: make signal.c respect user namespaces (v4) Serge Hallyn
2011-10-18 21:54 ` [PATCH 4/9] User namespace: don't allow sysctl in non-init user ns (v2) Serge Hallyn
2011-10-18 21:54 ` [PATCH 5/9] user namespace: clamp down users of cap_raised Serge Hallyn
2011-10-19 4:33 ` Andrew G. Morgan
2011-10-20 13:01 ` Serge E. Hallyn
2011-10-19 9:01 ` David Howells
2011-10-20 13:16 ` Serge E. Hallyn
2011-10-24 14:43 ` [PATCH 05/10] " Serge E. Hallyn
2011-10-24 15:47 ` Andrew G. Morgan
2011-10-24 17:28 ` Serge E. Hallyn
2011-10-25 0:43 ` Andrew G. Morgan
2011-10-25 3:03 ` Serge E. Hallyn
2011-10-25 17:33 ` Eric Paris
2011-10-25 20:09 ` Serge E. Hallyn
2011-10-18 21:54 ` [PATCH 6/9] Add Documentation/namespaces/user_namespace.txt (v3) Serge Hallyn
2011-10-18 21:54 ` [PATCH 7/9] user namespace: make each net (net_ns) belong to a user_ns Serge Hallyn
2011-10-18 21:54 ` [PATCH 8/9] protect cap_netlink_recv from user namespaces Serge Hallyn
2011-10-18 21:54 ` [PATCH 9/9] make net/core/scm.c uid comparisons user namespace aware Serge Hallyn
2011-10-18 22:14 ` Joe Perches
2011-10-18 23:22 ` Serge E. Hallyn
2011-10-19 2:25 ` [PATCH 9/9] make net/core/scm.c uid comparisons user namespace aware (v2) Serge E. Hallyn
2011-10-19 13:52 ` [PATCH 9/9] make net/core/scm.c uid comparisons user namespace aware Eric W. Biederman
2011-10-20 12:58 ` Serge E. Hallyn
2011-10-20 13:35 ` Eric W. Biederman
2011-10-20 14:14 ` Serge E. Hallyn
2011-10-24 4:15 ` Serge E. Hallyn
2011-10-24 4:27 ` Eric W. Biederman
2011-10-20 14:24 ` Serge E. Hallyn
2011-10-19 9:36 ` [PATCH 6/9] Add Documentation/namespaces/user_namespace.txt (v3) David Howells
2011-10-20 12:58 ` Serge E. Hallyn
2011-10-26 20:33 ` [PATCH 06/10] Add Documentation/namespaces/user_namespace.txt (v4) Serge E. Hallyn
2011-11-04 22:24 user namespaces: fix some uid/privilege leaks Serge Hallyn
2011-11-11 4:13 ` 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=1318974898-21431-1-git-send-email-serge@hallyn.com \
--to=serge@hallyn.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=oleg@redhat.com \
--cc=richard@nod.at \
--cc=segoon@openwall.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
all inboxes | Powered by JetHome®