Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Roman Demidov <roman.demidov.nn@gmail.com>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org,
	Joachim Vandersmissen <git@jvdsn.com>
Subject: Re: [PATCH 5.10] crypto: ecdh - explicitly zeroize private_key
Date: Sat, 31 Oct 2026 12:01:12 +0100	[thread overview]
Message-ID: <2026103104-wasabi-durably-9e01@gregkh> (raw)
In-Reply-To: <20260911123140.137198-1-roman.demidov.nn@gmail.com>

On Fri, Sep 11, 2026 at 03:31:37PM +0300, Roman Demidov wrote:
> From: Joachim Vandersmissen <git@jvdsn.com>
> 
> commit 73e5984e540a76a2ee1868b91590c922da8c24c9 upstream.
> 
> private_key is overwritten with the key parameter passed in by the
> caller (if present), or alternatively a newly generated private key.
> However, it is possible that the caller provides a key (or the newly
> generated key) which is shorter than the previous key. In that
> scenario, some key material from the previous key would not be
> overwritten. The easiest solution is to explicitly zeroize the entire
> private_key array first.
> 
> Note that this patch slightly changes the behavior of this function:
> previously, if the ecc_gen_privkey failed, the old private_key would
> remain. Now, the private_key is always zeroized. This behavior is
> consistent with the case where params.key is set and ecc_is_key_valid
> fails.
> 
> Signed-off-by: Joachim Vandersmissen <git@jvdsn.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> [ Roman: The zeroing is performed before ecdh_supported_curve() which is
> not present in upstream but this does not change the fix's logic. ]
> Signed-off-by: Roman Demidov <roman.demidov.nn@gmail.com>
> ---
> Backport fix for BDU:2025-00987
> 
>  crypto/ecdh.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/crypto/ecdh.c b/crypto/ecdh.c
> index 96f80c8f8e30..2e7acfc42155 100644
> --- a/crypto/ecdh.c
> +++ b/crypto/ecdh.c
> @@ -43,6 +43,8 @@ static int ecdh_set_secret(struct crypto_kpp *tfm, const void *buf,
>  	    params.key_size > sizeof(ctx->private_key))
>  		return -EINVAL;
>  
> +	memset(ctx->private_key, 0, sizeof(ctx->private_key));
> +
>  	ndigits = ecdh_supported_curve(params.curve_id);
>  	if (!ndigits)
>  		return -EINVAL;
> -- 
> 2.53.0
> 
> 

Does not apply to 5.10.y :(

      reply	other threads:[~2026-10-31 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 12:31 [PATCH 5.10] crypto: ecdh - explicitly zeroize private_key Roman Demidov
2026-10-31 11:01 ` Greg KH [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=2026103104-wasabi-durably-9e01@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=git@jvdsn.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=roman.demidov.nn@gmail.com \
    --cc=stable@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