Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964878AbZIEAWB (ORCPT ); Fri, 4 Sep 2009 20:22:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964861AbZIEAVt (ORCPT ); Fri, 4 Sep 2009 20:21:49 -0400 Received: from kroah.org ([198.145.64.141]:42367 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934641AbZIEAVj (ORCPT ); Fri, 4 Sep 2009 20:21:39 -0400 X-Mailbox-Line: From gregkh@mini.kroah.org Fri Sep 4 17:14:58 2009 Message-Id: <20090905001458.408910951@mini.kroah.org> User-Agent: quilt/0.48-1 Date: Fri, 04 Sep 2009 17:14:45 -0700 From: Greg KH To: linux-kernel@vger.kernel.org, stable@kernel.org Cc: stable-review@kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, Eric Dumazet , "David S. Miller" Subject: [patch 70/71] rose: Fix rose_getname() leak References: <20090905001335.106974681@mini.kroah.org> Content-Disposition: inline; filename=rose-fix-rose_getname-leak.patch In-Reply-To: <20090905001824.GA18171@kroah.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 25 2.6.30-stable review patch. If anyone has any objections, please let us know. ------------------ From: Eric Dumazet commit 17ac2e9c58b69a1e25460a568eae1b0dc0188c25 upstream. rose_getname() can leak kernel memory to user. Signed-off-by: Eric Dumazet Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman --- net/rose/af_rose.c | 1 + 1 file changed, 1 insertion(+) --- a/net/rose/af_rose.c +++ b/net/rose/af_rose.c @@ -957,6 +957,7 @@ static int rose_getname(struct socket *s struct rose_sock *rose = rose_sk(sk); int n; + memset(srose, 0, sizeof(*srose)); if (peer != 0) { if (sk->sk_state != TCP_ESTABLISHED) return -ENOTCONN; -- 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/