aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2012-04-04 11:40:19 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-13 08:14:07 -0700
commit41ae97bd8c2166184bf0552b7c41868b74344039 (patch)
tree5bd04d01e3712e41e31a4100105e27f9b2e24f3e /scripts
parent52a77de9f23e3b3d88354ee59a8923d566935abd (diff)
downloadkernel_samsung_smdk4412-41ae97bd8c2166184bf0552b7c41868b74344039.zip
kernel_samsung_smdk4412-41ae97bd8c2166184bf0552b7c41868b74344039.tar.gz
kernel_samsung_smdk4412-41ae97bd8c2166184bf0552b7c41868b74344039.tar.bz2
sysctl: fix write access to dmesg_restrict/kptr_restrict
commit 620f6e8e855d6d447688a5f67a4e176944a084e8 upstream. Commit bfdc0b4 adds code to restrict access to dmesg_restrict, however, it incorrectly alters kptr_restrict rather than dmesg_restrict. The original patch from Richard Weinberger (https://lkml.org/lkml/2011/3/14/362) alters dmesg_restrict as expected, and so the patch seems to have been misapplied. This adds the CAP_SYS_ADMIN check to both dmesg_restrict and kptr_restrict, since both are sensitive. Reported-by: Phillip Lougher <plougher@redhat.com> Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Serge Hallyn <serge.hallyn@canonical.com> Acked-by: Richard Weinberger <richard@nod.at> Signed-off-by: James Morris <james.l.morris@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions