From: Andi Kleen <andi@firstfloor.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dan Rosenberg <drosenberg@vsecurity.com>,
"chas\@cmf.nrl.navy.mil" <chas@cmf.nrl.navy.mil>,
"davem\@davemloft.net" <davem@davemloft.net>,
"kuznet\@ms2.inr.ac.ru" <kuznet@ms2.inr.ac.ru>,
"pekkas\@netcore.fi" <pekkas@netcore.fi>,
"jmorris\@namei.org" <jmorris@namei.org>,
"yoshfuji\@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
"kaber\@trash.net" <kaber@trash.net>,
"remi.denis-courmont\@nokia.com" <remi.denis-courmont@nokia.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"security\@kernel.org" <security@kernel.org>
Subject: Re: [Security] [SECURITY] Fix leaking of kernel heap addresses via /proc
Date: Sun, 07 Nov 2010 22:52:22 +0100 [thread overview]
Message-ID: <87sjzcssx5.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20101106234840.GD2935@thunk.org> (Ted Ts'o's message of "Sat, 6 Nov 2010 19:48:40 -0400")
Ted Ts'o <tytso@mit.edu> writes:
> Are there any userspace programs that might be reasonably expected to
> _use_ this information? If there is, we could just pick a random
> number at boot time, and then XOR the heap adddress with that random
> number.
If any of the addresses can be guessed ever (and that is likely if it's
allocated at boot) determining the random value will be trivial
for everyone.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-11-07 21:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:11 [SECURITY] Fix leaking of kernel heap addresses via /proc Dan Rosenberg
2010-11-06 20:50 ` [Security] " Linus Torvalds
2010-11-06 23:48 ` Ted Ts'o
2010-11-07 21:52 ` Andi Kleen [this message]
2010-11-07 22:48 ` Chas Williams (CONTRACTOR)
2010-11-07 23:14 ` Andi Kleen
2010-11-07 23:22 ` Linus Torvalds
2010-11-07 23:29 ` Andi Kleen
2010-11-07 23:27 ` Dan Rosenberg
2010-11-07 23:56 ` Andi Kleen
2010-11-08 2:01 ` David Miller
2010-11-08 7:33 ` Eric Dumazet
2010-11-08 9:43 ` Andi Kleen
2010-11-08 10:14 ` Eric Dumazet
2010-11-06 23:57 ` David Miller
2010-11-07 10:28 ` Oliver Hartkopp
2010-11-07 17:11 ` Ben Hutchings
2010-11-08 1:00 ` Willy Tarreau
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=87sjzcssx5.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@davemloft.net \
--cc=drosenberg@vsecurity.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=remi.denis-courmont@nokia.com \
--cc=security@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.