[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111212113156.GA12141@albatros>
Date: Mon, 12 Dec 2011 15:31:56 +0400
From: Vasiliy Kulikov <segoon@...nwall.com>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>,
kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org,
Hugh Dickins <hughd@...gle.com>
Subject: Re: [PATCH -next] proc: fix task_struct infoleak
On Sun, Dec 11, 2011 at 20:59 +0000, Al Viro wrote:
> On Sun, Dec 11, 2011 at 10:28:21PM +0400, Vasiliy Kulikov wrote:
> > proc_pid_permission() doesn't put task_struct on every /proc/$pid/
> > access. A demo from Hugh Dickins:
> >
> > while :; do ps; grep KernelStack /proc/meminfo; sleep 1; done
> >
> > Reported-by: Hugh Dickins <hughd@...gle.com>
> > Signed-off-by: Vasiliy Kulikov <segoon@...nwall.com>
> > ---
> > This is a patch against a hidepid patchset from -mm.
>
> Choose saner commit summary, please. It's not information leak, for pity sake
> - it's a plain and simple memory leak...
Oops! s/infoleak/memleak/ surely, bad habit...
Thank you, I'll resend the patch.
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
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.
