[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101116104600.GA24015@suse.de>
Date: Tue, 16 Nov 2010 11:46:03 +0100
From: Marcus Meissner <meissner@...e.de>
To: torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
tj@...nel.org, akpm@...l.org, hpa@...or.com, mingo@...e.hu,
w@....eu, alan@...rguk.ukuu.org.uk
Subject: [PATCH] kernel: make /proc/kallsyms mode 400 to reduce ease of
attacking
Hi,
Making /proc/kallsyms readable only for root makes it harder
for attackers to write generic kernel exploits by removing
one source of knowledge where things are in the kernel.
This is the second submit, discussion happened on this on first submit
and mostly concerned that this is just one hole of the sieve ... but
one of the bigger ones.
Changing the permissions of at least System.map and vmlinux is
also required to fix the same set, but a packaging issue.
Target of this starter patch and follow ups is removing any kind of
kernel space address information leak from the kernel.
Ciao, Marcus
Signed-off-by: Marcus Meissner <meissner@...e.de>
Acked-by: Tejun Heo <tj@...nel.org>
Acked-by: Eugene Teo <eugeneteo@...nel.org>
Reviewed-by: Jesper Juhl <jj@...osbits.net>
---
kernel/kallsyms.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c
index 6f6d091..a8db257 100644
--- a/kernel/kallsyms.c
+++ b/kernel/kallsyms.c
@@ -546,7 +546,7 @@ static const struct file_operations kallsyms_operations = {
static int __init kallsyms_init(void)
{
- proc_create("kallsyms", 0444, NULL, &kallsyms_operations);
+ proc_create("kallsyms", 0400, NULL, &kallsyms_operations);
return 0;
}
device_initcall(kallsyms_init);
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists