mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: wusbcore: crypto: Remove VLA usage
Date: Fri, 16 Mar 2018 08:19:31 -0500	[thread overview]
Message-ID: <54e89cea-a1a1-90a3-912f-209172bb41ae@embeddedor.com> (raw)
In-Reply-To: <20180316130141.GA22594@embeddedgus>


I just discovered an issue with this patch. Please, drop it. I'll send 
v2 shortly.

Thanks
--
Gustavo

On 03/16/2018 08:01 AM, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wvla, remove VLA and replace it
> with dynamic memory allocation instead.
> 
> The use of stack Variable Length Arrays needs to be avoided, as they
> can be a vector for stack exhaustion, which can be both a runtime bug
> or a security flaw. Also, in general, as code evolves it is easy to
> lose track of how big a VLA can get. Thus, we can end up having runtime
> failures that are hard to debug.
> 
> Also, fixed as part of the directive to remove all VLAs from
> the kernel: https://lkml.org/lkml/2018/3/7/621
> 
> Notice that in this particular case, an alternative to kzalloc is kcalloc,
> in which case the code would look as follows instead:
> 
> iv = kcalloc(crypto_skcipher_ivsize(tfm_cbc), sizeof(*iv), GFP_KERNEL);
> 
> but if the data type of _iv_ never changes, or the type size is always one
> byte, kzalloc is good enough.
> 
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
>   drivers/usb/wusbcore/crypto.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/wusbcore/crypto.c b/drivers/usb/wusbcore/crypto.c
> index 4c00be2d..3511473 100644
> --- a/drivers/usb/wusbcore/crypto.c
> +++ b/drivers/usb/wusbcore/crypto.c
> @@ -202,7 +202,7 @@ static int wusb_ccm_mac(struct crypto_skcipher *tfm_cbc,
>   	struct scatterlist sg[4], sg_dst;
>   	void *dst_buf;
>   	size_t dst_size;
> -	u8 iv[crypto_skcipher_ivsize(tfm_cbc)];
> +	u8 *iv;
>   	size_t zero_padding;
>   
>   	/*
> @@ -222,9 +222,11 @@ static int wusb_ccm_mac(struct crypto_skcipher *tfm_cbc,
>   		zero_padding;
>   	dst_buf = kzalloc(dst_size, GFP_KERNEL);
>   	if (!dst_buf)
> -		goto error_dst_buf;
> +		goto error_alloc;
>   
> -	memset(iv, 0, sizeof(iv));
> +	iv = kzalloc(crypto_skcipher_ivsize(tfm_cbc), GFP_KERNEL);
> +	if (!iv)
> +		goto error_alloc;
>   
>   	/* Setup B0 */
>   	scratch->b0.flags = 0x59;	/* Format B0 */
> @@ -276,8 +278,9 @@ static int wusb_ccm_mac(struct crypto_skcipher *tfm_cbc,
>   	bytewise_xor(mic, &scratch->ax, iv, 8);
>   	result = 8;
>   error_cbc_crypt:
> +	kfree(iv);
>   	kfree(dst_buf);
> -error_dst_buf:
> +error_alloc:
>   	return result;
>   }
>   
> 

      reply	other threads:[~2018-03-16 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 13:01 Gustavo A. R. Silva
2018-03-16 13:19 ` Gustavo A. R. Silva [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54e89cea-a1a1-90a3-912f-209172bb41ae@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®