Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Antoine Tenart <atenart@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
Subject: Re: [PATCH] crypto: inside-secure - Zeroize temporary arrays on stack with sensitive data
Date: Wed, 19 Aug 2026 09:40:48 +0200	[thread overview]
Message-ID: <aoVdMMJJH--AZpL9@kwain> (raw)
In-Reply-To: <20260814083651.59535-1-thuth@redhat.com>

On Fri, Aug 14, 2026 at 10:36:51AM +0200, Thomas Huth wrote:
> This issue has been found by the Sashiko bot while reviewing another
> patch: key_tmp[] in safexcel_xcbcmac_setkey() and consts[] / _const[]
> in safexcel_cmac_setkey() contain crypto key material that should not
> get exposed to the outside once the function is done. Scrub the arrays
> with memzero_explicit() to avoid that the data could leak via the stack.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>

This could have both a Reported-by (Sashiko) and a Fixes tag.

With that,

Acked-by: Antoine Tenart <atenart@kernel.org>

Thanks!

> ---
>  drivers/crypto/inside-secure/safexcel_hash.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/crypto/inside-secure/safexcel_hash.c b/drivers/crypto/inside-secure/safexcel_hash.c
> index 3402e570d045c..1ae6fbec31298 100644
> --- a/drivers/crypto/inside-secure/safexcel_hash.c
> +++ b/drivers/crypto/inside-secure/safexcel_hash.c
> @@ -1993,6 +1993,7 @@ static int safexcel_xcbcmac_setkey(struct crypto_ahash *tfm, const u8 *key,
>  	ret = aes_prepareenckey(ctx->aes,
>  				(u8 *)key_tmp + 2 * AES_BLOCK_SIZE,
>  				AES_MIN_KEY_SIZE);
> +	memzero_explicit(key_tmp, sizeof(key_tmp));
>  	if (ret)
>  		return ret;
>  
> @@ -2104,6 +2105,9 @@ static int safexcel_cmac_setkey(struct crypto_ahash *tfm, const u8 *key,
>  	}
>  	ctx->cbcmac = false;
>  
> +
> +	memzero_explicit(consts, sizeof(consts));
> +	memzero_explicit(_const, sizeof(_const));
>  	return 0;
>  }
>  
> -- 
> 2.55.0
> 

      reply	other threads:[~2026-08-19  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  8:36 [PATCH] crypto: inside-secure - Zeroize temporary arrays on stack with sensitive data Thomas Huth
2026-08-19  7:40 ` Antoine Tenart [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=aoVdMMJJH--AZpL9@kwain \
    --to=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thuth@redhat.com \
    /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