linux-kernel - Re: [PATCH] exofs: check for allocation failure in uri

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Aug 2012 11:54:19 -0700
From:	Sachin Bhamare <sbhamare@...asas.com>
To:	Alexey Khoroshilov <khoroshilov@...ras.ru>
CC:	Boaz Harrosh <bharrosh@...asas.com>,
	Benny Halevy <bhalevy@...ian.com>, <osd-dev@...n-osd.org>,
	<linux-kernel@...r.kernel.org>, <ldv-project@...ras.ru>
Subject: Re: [PATCH] exofs: check for allocation failure in uri_store()

On 8/8/12 10:02 AM, Alexey Khoroshilov wrote:
> There is no memory allocation failure check in uri_store().
> That can lead to NULL pointer dereference.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@...ras.ru>
> ---
>  fs/exofs/sys.c |    7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/exofs/sys.c b/fs/exofs/sys.c
> index 5a7b691..1b4f2f9 100644
> --- a/fs/exofs/sys.c
> +++ b/fs/exofs/sys.c
> @@ -80,8 +80,13 @@ static ssize_t uri_show(struct exofs_dev *edp, char *buf)
>  
>  static ssize_t uri_store(struct exofs_dev *edp, const char *buf, size_t len)
>  {
> +	uint8_t *new_uri;
> +
>  	edp->urilen = strlen(buf) + 1;
> -	edp->uri = krealloc(edp->uri, edp->urilen, GFP_KERNEL);
> +	new_uri = krealloc(edp->uri, edp->urilen, GFP_KERNEL);
> +	if (new_uri == NULL)
> +		return -ENOMEM;
> +	edp->uri = new_uri;
>  	strncpy(edp->uri, buf, edp->urilen);
>  	return edp->urilen;
>  }
Ack-by : Sachin Bhamare <sbhamare@...asas.com>
--
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/