From: Pekka Enberg <penberg@kernel.org>
To: Kees Cook <kees.cook@canonical.com>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>,
"David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH] ipc: explicitly clear stack memory in user structs
Date: Tue, 09 Nov 2010 22:51:47 +0200 [thread overview]
Message-ID: <4CD9B463.6090504@kernel.org> (raw)
In-Reply-To: <20101109205008.GU5876@outflux.net>
On 9.11.2010 22.50, Kees Cook wrote:
> Hi Pekka,
>
> On Tue, Nov 09, 2010 at 10:43:07PM +0200, Pekka Enberg wrote:
>> On Tue, Oct 26, 2010 at 2:58 AM, Kees Cook<kees.cook@canonical.com> wrote:
>>> CVE-2010-4072
>>>
>>> The old shm interface will leak a few bytes of stack contents. Explicitly
>>> clear structure using memset instead of C99-style initialization in case
>>> there are ever holes in the packing.
>>>
>>> Cc: stable<stable@kernel.org>
>>> Signed-off-by: Kees Cook<kees.cook@canonical.com>
>> This looks like a genuine bug fix but I don't see this patch in
>> mainline. Why is that?
> No one has committed it. I don't know why; I've sent it a few times now.
Andrew, would you mind picking this up and route it to the appropriate
person if necessary?
Acked-by: Pekka Enberg <penberg@kernel.org>
Pekka
next prev parent reply other threads:[~2010-11-09 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 23:58 [PATCH] ipc: explicitly clear stack memory in user structs Kees Cook
2010-11-09 20:43 ` Pekka Enberg
2010-11-09 20:50 ` Kees Cook
2010-11-09 20:51 ` Pekka Enberg [this message]
2010-11-09 21:34 ` Pekka Enberg
2010-11-09 21:49 ` Kees Cook
2010-11-09 22:46 ` Linus Torvalds
2010-11-09 23:09 ` Andrew Morton
2010-11-09 23:48 ` Kees Cook
2010-11-10 0:54 ` Linus Torvalds
2010-11-10 1:03 ` Joe Perches
2010-11-10 2:00 ` Kees Cook
2010-11-11 7:37 ` 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=4CD9B463.6090504@kernel.org \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hughd@google.com \
--cc=jslaby@suse.cz \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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