diff options
author | Kees Cook <keescook@chromium.org> | 2012-03-19 16:12:53 -0700 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2012-03-29 11:37:17 +0200 |
commit | bdbb776f882f5ad431aa1e694c69c1c3d6a4a5b8 (patch) | |
tree | 854b6b5869857d40a02d21bb51b375812bdb2ed0 /security | |
parent | b5174fa3a7f4f8f150bfa3b917c92608953dfa0f (diff) | |
download | linux-bdbb776f882f5ad431aa1e694c69c1c3d6a4a5b8.tar.bz2 |
futex: Do not leak robust list to unprivileged process
It was possible to extract the robust list head address from a setuid
process if it had used set_robust_list(), allowing an ASLR info leak. This
changes the permission checks to be the same as those used for similar
info that comes out of /proc.
Running a setuid program that uses robust futexes would have had:
cred->euid != pcred->euid
cred->euid == pcred->uid
so the old permissions check would allow it. I'm not aware of any setuid
programs that use robust futexes, so this is just a preventative measure.
(This patch is based on changes from grsecurity.)
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Jiri Kosina <jkosina@suse.cz>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: David Howells <dhowells@redhat.com>
Cc: Serge E. Hallyn <serge.hallyn@canonical.com>
Cc: kernel-hardening@lists.openwall.com
Cc: spender@grsecurity.net
Link: http://lkml.kernel.org/r/20120319231253.GA20893@www.outflux.net
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions