Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 27 Sep 2011 21:56:42 +0400
From: Vasiliy Kulikov <>
	Christoph Lameter <>,
	Pekka Enberg <>, Matt Mackall <>,
	Andrew Morton <>
Cc:, Kees Cook <>,
	Dave Hansen <>,,
	Linus Torvalds <>,
	David Rientjes <>,
	Alan Cox <>,
Subject: [PATCH 2/2] mm: restrict access to /proc/meminfo

/proc/meminfo stores information related to memory pages usage, which
may be used to monitor the number of objects in specific caches (and/or
the changes of these numbers).  This might reveal private information
similar to /proc/slabinfo infoleaks.  To remove the infoleak, just
restrict meminfo to root.  If it is used by unprivileged daemons,
meminfo permissions can be altered the same way as slabinfo:

    groupadd meminfo
    usermod -a -G meminfo $MONITOR_USER
    chmod g+r /proc/meminfo
    chgrp meminfo /proc/meminfo

Signed-off-by: Vasiliy Kulikov <>
CC: Kees Cook <>
CC: Dave Hansen <>
CC: Christoph Lameter <>
CC: Pekka Enberg <>
CC: Linus Torvalds <>
CC: David Rientjes <>
CC: Alan Cox <>
 fs/proc/meminfo.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
index 5861741..949bdee 100644
--- a/fs/proc/meminfo.c
+++ b/fs/proc/meminfo.c
@@ -187,7 +187,7 @@ static const struct file_operations meminfo_proc_fops = {
 static int __init proc_meminfo_init(void)
-	proc_create("meminfo", 0, NULL, &meminfo_proc_fops);
+	proc_create("meminfo", S_IFREG | S_IRUSR, NULL, &meminfo_proc_fops);
 	return 0;

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.