Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754941Ab0KIUvp (ORCPT ); Tue, 9 Nov 2010 15:51:45 -0500 Received: from freeflow.nu ([178.79.134.28]:53438 "EHLO freeflow.nu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753151Ab0KIUvn (ORCPT ); Tue, 9 Nov 2010 15:51:43 -0500 Message-ID: <4CD9B463.6090504@kernel.org> Date: Tue, 09 Nov 2010 22:51:47 +0200 From: Pekka Enberg User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Kees Cook CC: linux-kernel@vger.kernel.org, Al Viro , Andrew Morton , Jiri Slaby , "David S. Miller" , Linus Torvalds , Hugh Dickins , Manfred Spraul Subject: Re: [PATCH] ipc: explicitly clear stack memory in user structs References: <20101025235804.GA11760@outflux.net> <20101109205008.GU5876@outflux.net> In-Reply-To: <20101109205008.GU5876@outflux.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1076 Lines: 28 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 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 >>> Signed-off-by: Kees Cook >> 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 Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/