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
| ||
|
Date: Thu, 18 Feb 2016 20:47:42 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Geert Uytterhoeven <geert+renesas@...der.be> Cc: Alexandre Courbot <gnurou@...il.com>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, linux-renesas-soc@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH -next] gpio: Use kzalloc() to allocate struct gpio_device to fix crash On Tue, Feb 16, 2016 at 11:22 AM, Geert Uytterhoeven <geert+renesas@...der.be> wrote: > gpiochip_add_data() allocates the struct gpio_device using kmalloc(), > which doesn't zero the returned memory. > > Hence when calling dev_set_name(), it may try to free a bogus old name, > causing a crash: Ooops got two patches to this independently and applied the other one, I tagged your name onto the Reported-by now. Thanks! Yours, Linus Walleij
Powered by blists - more mailing lists