linux-kernel - Re: [PATCH] drivers: avoid use after free of a pinctrl context pointer

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20130118013743.GA7605@kroah.com>
Date:	Thu, 17 Jan 2013 17:37:43 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers: avoid use after free of a pinctrl context
 pointer

On Wed, Jan 16, 2013 at 05:22:34PM +0100, Guennadi Liakhovetski wrote:
> During probing, pinctrl context is allocated and assigned to the struct
> device::pins pointer. If probing fails or if the driver is later unbound
> and re-probed again, the memory is freed, but the pointer is not cleared.
> On a repeated probing attempt a non-NULL pointer indicates an already
> allocated context, which then gets used. To avoid this the pointer must
> be cleared.
> 
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@....de>
> ---
>  drivers/base/dd.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)

This can't go through my tree, as it breaks the build.  Please send it
to whereever the pinctrl code is coming from.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/