From: Valdis.Kletnieks@vt.edu
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@gentwo.org>,
kernel-hardening@lists.openwall.com,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Kees Cook <kees@ubuntu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
Date: Thu, 29 Sep 2011 12:57:32 -0400 [thread overview]
Message-ID: <23921.1317315452@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 29 Sep 2011 20:18:48 +0400." <20110929161848.GA16348@albatros>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Thu, 29 Sep 2011 20:18:48 +0400, Vasiliy Kulikov said:
> As `new' is just increased, it means it is known with KB granularity,
> not MB. By counting used slab objects he learns filled_obj_size_sum.
>
> So, rounding gives us nothing, but obscurity.
Yes, but if he has an exploit that requires using up (for example) exactly 31
objects in the slab, he may now know that a new slab got allocated to push it
over the MB boundary. So he knows there's exactly one object in that new slab.
But now he has to fly blind for the next 30 because the numbers will display
exactly the same, and he can't correct for somebody else allocating one so he
needs to only allocate 29...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-09-29 16:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:54 [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Vasiliy Kulikov
2011-09-27 17:56 ` [PATCH 2/2] mm: restrict access to /proc/meminfo Vasiliy Kulikov
2011-09-27 18:27 ` David Rientjes
2011-09-27 19:14 ` Vasiliy Kulikov
2011-09-27 19:38 ` Vasiliy Kulikov
2011-09-27 20:03 ` Christoph Lameter
2011-09-27 20:33 ` David Rientjes
2011-09-27 20:47 ` Christoph Lameter
2011-09-28 20:31 ` Dave Hansen
2011-09-28 20:52 ` Alan Cox
2011-09-29 0:43 ` Valdis.Kletnieks
2011-09-29 14:11 ` Christoph Lameter
2011-09-29 16:18 ` Vasiliy Kulikov
2011-09-29 16:30 ` Dave Hansen
2011-09-29 16:43 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 16:57 ` Valdis.Kletnieks [this message]
2011-09-29 17:25 ` Vasiliy Kulikov
2011-09-29 17:28 ` Vasiliy Kulikov
2011-09-28 21:46 ` Andrew Morton
2011-09-30 19:53 ` Vasiliy Kulikov
2011-09-30 20:03 ` Andrew Morton
2011-09-30 20:12 ` Vasiliy Kulikov
2011-09-30 20:15 ` Dave Hansen
2011-09-27 18:08 ` [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Christoph Lameter
2011-09-27 19:16 ` Vasiliy Kulikov
2011-09-27 19:35 ` Christoph Lameter
2011-09-27 18:21 ` David Rientjes
2011-09-27 20:00 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23921.1317315452@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=cl@gentwo.org \
--cc=dave@linux.vnet.ibm.com \
--cc=kees@ubuntu.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=segoon@openwall.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®