linux-kernel - Re: [PATCH][V3] usb: isp1760: check for null return from kzalloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Jun 2015 10:38:00 -0500
From:	Felipe Balbi <balbi@...com>
To:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
CC:	Colin King <colin.king@...onical.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Felipe Balbi <balbi@...com>,
	Sudeep Holla <sudeep.holla@....com>,
	Valentin Rothberg <Valentin.Rothberg@...6.fr>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][V3] usb: isp1760: check for null return from kzalloc

Hi,

On Wed, Jun 03, 2015 at 03:43:23AM +0300, Laurent Pinchart wrote:
> > From: Colin Ian King <colin.king@...onical.com>
> > 
> > isp1760_ep_alloc_request allocates a structure with kzalloc without checking
> > for NULL and then returns a pointer to one of the structure fields. As the
> > field happens to be the first in the structure the caller can properly
> > check for NULL, but this is risky if the structure layout is changed later.
> > Add an explicit NULL check for the kzalloc return value
> > 
> > Detected with smatch static analysis:
> > 
> > drivers/usb/isp1760/isp1760-udc.c:816 isp1760_ep_alloc_request()
> >   error: potential null dereference 'req'.  (kzalloc returns null)
> > 
> > [ thanks to Laurent Pinchart for improved commit message ]
> > 
> > Signed-off-by: Colin Ian King <colin.king@...onical.com>
> 
> Acked-by: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> 
> Felipe, I expect you to pick this up, please let me know if there's any issue.

once -rc1 is tagged, yes. My tree is already closed for v4.2.

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)