From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932581AbcAaAiA (ORCPT ); Sat, 30 Jan 2016 19:38:00 -0500 Received: from mail-yk0-f194.google.com ([209.85.160.194]:35617 "EHLO mail-yk0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932134AbcAaAh7 (ORCPT ); Sat, 30 Jan 2016 19:37:59 -0500 From: Joshua Clayton To: Dan Carpenter Cc: Larry Finger , Florian Schilhabel , Greg Kroah-Hartman , Luis de Bethencourt , Punit Vara , Andy Shevchenko , Aya Mahfouz , Alison Schofield , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: Re: [patch] staging: rtl8712: memory corruption in wpa_set_encryption() Date: Sat, 30 Jan 2016 16:37:49 -0800 Message-ID: <2214433.RePI7YjxKq@diplodocus> User-Agent: KMail/4.14.10 (Linux/4.3.3-gentoo; KDE/4.14.16; x86_64; ; ) In-Reply-To: <20160130144110.GE3462@mwanda> References: <20160130144110.GE3462@mwanda> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday, January 30, 2016 05:41:10 PM Dan Carpenter wrote: > ->KeyMaterial is declared as a 16 byte array, but we only ever allocate > either 5 or 13 bytes of it. The problem is that we memset() all 16 > bytes to zero so we're memsetting past the end of the allocated memory. > > I fixed this in slightly lazy way, by just allocating 16 bytes. This > works but there is a lot more cleanup you could do to this code if you > wanted. Which is why this code is in staging. Better in every way than a crazy variable alloc if you ask me. > > Signed-off-by: Dan Carpenter > > diff --git a/drivers/staging/rtl8712/rtl871x_ioctl_linux.c b/drivers/staging/rtl8712/rtl871x_ioctl_linux.c > index edfc680..db2e31bc 100644 > --- a/drivers/staging/rtl8712/rtl871x_ioctl_linux.c > +++ b/drivers/staging/rtl8712/rtl871x_ioctl_linux.c > @@ -398,12 +398,9 @@ static int wpa_set_encryption(struct net_device *dev, struct ieee_param *param, > wep_key_idx = 0; > if (wep_key_len > 0) { > wep_key_len = wep_key_len <= 5 ? 5 : 13; > - pwep = kmalloc((u32)(wep_key_len + > - FIELD_OFFSET(struct NDIS_802_11_WEP, > - KeyMaterial)), GFP_ATOMIC); > + pwep = kzalloc(sizeof(*pwep), GFP_ATOMIC); > if (pwep == NULL) > return -ENOMEM; > - memset(pwep, 0, sizeof(struct NDIS_802_11_WEP)); Should there be a newline after the "if" statement? > pwep->KeyLength = wep_key_len; > pwep->Length = wep_key_len + > FIELD_OFFSET(struct NDIS_802_11_WEP,