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: <201005152201.59885.florian@openwrt.org>
Date:	Sat, 15 May 2010 22:01:58 +0200
From:	Florian Fainelli <florian@...nwrt.org>
To:	Samuel Ortiz <sameo@...ux.intel.com>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH] MFD: prevent null pointer dereference in mfd_add_device

Hi Samuel,

I just saw that your for-next branch contains the proper fix, this patch can be 
discarded.

Le samedi 15 mai 2010 21:57:10, Florian Fainelli a écrit :
> If a driver calls mfd_add_device with a NULL argument for the mem_base
>  resource we will end up dereferencing it without checking for its validity
>  here: res[r].start = mem_base->start cell->resources[r].start; (line 53 of
>  mfd-core.c)
> 
> This patch adds the checking on the mem_base argument and bails out
>  accordingly if it is NULL.
> 
> Signed-off-by: Florian Fainelli <florian@...nwrt.org>
> CC: stable@...nel.org
> ---
> diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
> index 8ffbb7a..f890b27 100644
> --- a/drivers/mfd/mfd-core.c
> +++ b/drivers/mfd/mfd-core.c
> @@ -49,6 +49,8 @@ static int mfd_add_device(struct device *parent, int id,
> 
>  		/* Find out base to use */
>  		if (cell->resources[r].flags & IORESOURCE_MEM) {
> +			if (!mem_base)
> +				goto fail_res;
>  			res[r].parent = mem_base;
>  			res[r].start = mem_base->start +
>  				cell->resources[r].start;
> 

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ