diff options
| author | Eric W. Biederman <ebiederm@xmission.com> | 2013-03-25 19:57:10 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-09-26 17:18:28 -0700 |
| commit | 1ca91545961a92067cb8ad3ebc1558c8d1574456 (patch) | |
| tree | 5a36f10eb2f7f78e6b6c6ff7e8a5664dd264e614 /fs/proc | |
| parent | 8b89ae8a4914ee393c0db530735d933481272e97 (diff) | |
| download | linux-3.10-1ca91545961a92067cb8ad3ebc1558c8d1574456.tar.gz linux-3.10-1ca91545961a92067cb8ad3ebc1558c8d1574456.tar.bz2 linux-3.10-1ca91545961a92067cb8ad3ebc1558c8d1574456.zip | |
proc: Restrict mounting the proc filesystem
commit aee1c13dd0f6c2fc56e0e492b349ee8ac655880f upstream.
Don't allow mounting the proc filesystem unless the caller has
CAP_SYS_ADMIN rights over the pid namespace. The principle here is if
you create or have capabilities over it you can mount it, otherwise
you get to live with what other people have mounted.
Andy pointed out that this is needed to prevent users in a user
namespace from remounting proc and specifying different hidepid and gid
options on already existing proc mounts.
Reported-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/proc')
| -rw-r--r-- | fs/proc/root.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/proc/root.c b/fs/proc/root.c index 41a6ea93f48..04ec276c7ba 100644 --- a/fs/proc/root.c +++ b/fs/proc/root.c @@ -110,7 +110,8 @@ static struct dentry *proc_mount(struct file_system_type *fs_type, ns = task_active_pid_ns(current); options = data; - if (!current_user_ns()->may_mount_proc) + if (!current_user_ns()->may_mount_proc || + !ns_capable(ns->user_ns, CAP_SYS_ADMIN)) return ERR_PTR(-EPERM); } |