From: Herbert Xu <herbert@gondor.apana.org.au>
To: Seohyeon Maeng <bioloidgp@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] crypto: ccm - Set rfc4309 maxauthsize from child
Date: Mon, 20 Jul 2026 11:34:21 +1000 [thread overview]
Message-ID: <al17HaL8wNd_fuDc@gondor.apana.org.au> (raw)
In-Reply-To: <alu_daaywAIZXKZm@DESKTOP-SF55S0Q.localdomain>
On Sun, Jul 19, 2026 at 03:01:25AM +0900, Seohyeon Maeng wrote:
>
> Summary
> -------
>
> crypto_rfc4309_init_tfm() spawns its child AEAD but does not synchronize the
> child's initial authsize with the RFC4309 parent's initial authsize.
Thanks for the report. It should do the same thing as GCM and use
the child's maxauthsize.
---8<---
Set the maxauthsize of rfc4309 using that of the child algorithm.
Fixes: 4a49b499dfa0 ("[CRYPTO] ccm: Added CCM mode")
Reported-by: Seohyeon Maeng <bioloidgp@gmail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
diff --git a/crypto/ccm.c b/crypto/ccm.c
index 2ae929ffdef8..916441e4f2b8 100644
--- a/crypto/ccm.c
+++ b/crypto/ccm.c
@@ -747,7 +747,7 @@ static int crypto_rfc4309_create(struct crypto_template *tmpl,
inst->alg.ivsize = 8;
inst->alg.chunksize = crypto_aead_alg_chunksize(alg);
- inst->alg.maxauthsize = 16;
+ inst->alg.maxauthsize = crypto_aead_alg_maxauthsize(alg);
inst->alg.base.cra_ctxsize = sizeof(struct crypto_rfc4309_ctx);
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-07-20 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 18:01 [BUG] crypto: rfc4309 default authsize mismatch causes unprivileged AF_ALG panic Seohyeon Maeng
2026-07-20 1:34 ` Herbert Xu [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=al17HaL8wNd_fuDc@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=bioloidgp@gmail.com \
--cc=davem@davemloft.net \
--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