Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Steve French <smfrench@gmail.com>,
	Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [PATCH v2 0/6] crypto: Add __cleanup functions for zeroizing aes_cmac_key & aes_cmac_ctx
Date: Wed, 12 Aug 2026 18:59:13 -0700	[thread overview]
Message-ID: <20260813015913.GA28329@sol> (raw)
In-Reply-To: <20260807125845.1477067-1-thuth@redhat.com>

On Fri, Aug 07, 2026 at 02:58:37PM +0200, Thomas Huth wrote:
> Code that uses AES-CMAC might need to zeroize their local aes_cmac_key
> and/or aes_cmac_ctx structures after use to avoid leaking sensitive
> material on the stack.
> 
> The first patch introduces an aes_cmac_zeroize_key() and an
> aes_cmac_zeroize_ctx() helper function that can be used with __cleanup()
> to automatically clear the key and context when they go out of scope.
> 
> Patches 2 - 4 add the __cleanup markers to spots in the code that
> missed to clean up the structures so far.
> 
> The final two patches are just cosmetics and change some memzero_explicit()
> calls to use the __cleanup() way instead.
> 
> Note: There are more spots in the smb, tcp-ao and bluetooth code that
> need some zeroization of sensitive data on the stack. I will tackle
> those in later patches, this series here focuses on the new __cleanup
> wrappers.
> 
> v2:
> - Update comments and positions of the functions in the 1st patch
> - Also clear tmp[] in the bluetooth patch (the patch is pointless otherwise)
> 
> Thomas Huth (6):
>   crypto: Provide wrapper functions for zeroizing aes_cmac_key and
>     aes_cmac_ctx
>   smb: clear the aes_cmac_key and aes_cmac_ctx when done
>   net/tcp-ao: clear the aes_cmac_key when done
>   Bluetooth: SMP: clear the aes_cmac_key when done
>   lib/crypto: aes: Use _cleanup() for aes_cmac_key instead of
>     memzero_explicit()
>   mac80211: fils_aead: Use _cleanup for aes_cmac_key instead of
>     memzero_explicit
> 
>  fs/smb/client/smb2transport.c |  4 ++--
>  fs/smb/server/auth.c          |  2 +-
>  include/crypto/aes-cbc-macs.h | 34 ++++++++++++++++++++++++++++++++++
>  lib/crypto/aes.c              |  3 +--
>  net/bluetooth/smp.c           |  3 ++-
>  net/ipv4/tcp_ao.c             |  2 +-
>  net/mac80211/fils_aead.c      |  3 +--
>  7 files changed, 42 insertions(+), 9 deletions(-)

Applied all except patch 3 to
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next

- Eric

      parent reply	other threads:[~2026-08-13  2:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 12:58 [PATCH v2 0/6] crypto: Add __cleanup functions for zeroizing aes_cmac_key & aes_cmac_ctx Thomas Huth
2026-08-07 12:58 ` [PATCH v2 1/6] crypto: Provide wrapper functions for zeroizing aes_cmac_key and aes_cmac_ctx Thomas Huth
2026-08-07 12:58 ` [PATCH v2 2/6] smb: clear the aes_cmac_key and aes_cmac_ctx when done Thomas Huth
2026-08-11 10:31   ` Namjae Jeon
2026-08-11 12:57     ` Thomas Huth
2026-08-12 12:44       ` Namjae Jeon
2026-08-07 12:58 ` [PATCH v2 3/6] net/tcp-ao: clear the aes_cmac_key " Thomas Huth
2026-08-07 22:22   ` Jakub Kicinski
2026-08-08 10:38     ` Thomas Huth
2026-08-07 12:58 ` [PATCH v2 4/6] Bluetooth: SMP: " Thomas Huth
2026-08-07 12:58 ` [PATCH v2 5/6] lib/crypto: aes: Use __cleanup() for aes_cmac_key instead of memzero_explicit() Thomas Huth
2026-08-07 12:58 ` [PATCH v2 6/6] mac80211: fils_aead: " Thomas Huth
2026-08-07 13:00   ` Johannes Berg
2026-08-13  1:59 ` Eric Biggers [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=20260813015913.GA28329@sol \
    --to=ebiggers@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linkinjeon@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --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