From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: Kees Cook <keescook@chromium.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>,
<kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH] crypto/ecc: Remove stack VLA usage
Date: Thu, 8 Mar 2018 11:43:45 +0200 [thread overview]
Message-ID: <4fbe11f1-c92e-a4d5-616d-01e983f5405f@microchip.com> (raw)
In-Reply-To: <20180307215615.GA18928@beast>
Hi, Kees,
On 03/07/2018 11:56 PM, Kees Cook wrote:
> On the quest to remove all VLAs from the kernel[1], this switches to
> a pair of kmalloc regions instead of using the stack. This also moves
> the get_random_bytes() after all allocations (and drops the needless
> "nbytes" variable).
>
> [1] https://lkml.org/lkml/2018/3/7/621
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> crypto/ecc.c | 23 +++++++++++++++++------
> 1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/crypto/ecc.c b/crypto/ecc.c
> index 18f32f2a5e1c..5bfa63603da0 100644
> --- a/crypto/ecc.c
> +++ b/crypto/ecc.c
> @@ -1025,9 +1025,7 @@ int crypto_ecdh_shared_secret(unsigned int curve_id, unsigned int ndigits,
> {
> int ret = 0;
> struct ecc_point *product, *pk;
> - u64 priv[ndigits];
> - u64 rand_z[ndigits];
> - unsigned int nbytes;
> + u64 *priv, *rand_z;
> const struct ecc_curve *curve = ecc_get_curve(curve_id);
>
> if (!private_key || !public_key || !curve) {
> @@ -1035,14 +1033,22 @@ int crypto_ecdh_shared_secret(unsigned int curve_id, unsigned int ndigits,
> goto out;
> }
>
> - nbytes = ndigits << ECC_DIGITS_TO_BYTES_SHIFT;
> + priv = kmalloc_array(ndigits, sizeof(*priv), GFP_KERNEL);
> + if (!priv) {
> + ret = -ENOMEM;
> + goto out;
> + }
>
> - get_random_bytes(rand_z, nbytes);
> + rand_z = kmalloc_array(ndigits, sizeof(*rand_z), GFP_KERNEL);
> + if (!rand_z) {
> + ret = -ENOMEM;
> + goto kfree_out;
> + }
>
> pk = ecc_alloc_point(ndigits);
> if (!pk) {
> ret = -ENOMEM;
> - goto out;
> + goto kfree_out;
> }
>
> product = ecc_alloc_point(ndigits);
> @@ -1051,6 +1057,8 @@ int crypto_ecdh_shared_secret(unsigned int curve_id, unsigned int ndigits,
> goto err_alloc_product;
> }
>
> + get_random_bytes(rand_z, ndigits << ECC_DIGITS_TO_BYTES_SHIFT);
> +
> ecc_swap_digits(public_key, pk->x, ndigits);
> ecc_swap_digits(&public_key[ndigits], pk->y, ndigits);
> ecc_swap_digits(private_key, priv, ndigits);
> @@ -1065,6 +1073,9 @@ int crypto_ecdh_shared_secret(unsigned int curve_id, unsigned int ndigits,
> ecc_free_point(product);
> err_alloc_product:
> ecc_free_point(pk);
> +kfree_out:
> + kfree(priv);
I think we should use kzfree here.
> + kfree(rand_z);
Probably here too. Looks like there are few intermediate buffers in ecc
that should be zeroized as well.
Best,
ta
> out:
> return ret;
> }
>
next prev parent reply other threads:[~2018-03-08 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 21:56 Kees Cook
2018-03-08 9:43 ` Tudor Ambarus [this message]
2018-03-08 21:55 ` Kees Cook
2018-03-09 8:21 ` Tudor Ambarus
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=4fbe11f1-c92e-a4d5-616d-01e983f5405f@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome