From: Thorsten Blum <thorsten.blum@toblux.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
kees@kernel.org, gustavoars@kernel.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Thorsten Blum <thorsten.blum@toblux.com>
Subject: [PATCH] crypto: chacha20poly1305 - Annotate struct chachapoly_ctx with __counted_by()
Date: Mon, 5 Aug 2024 19:52:38 +0200 [thread overview]
Message-ID: <20240805175237.63098-2-thorsten.blum@toblux.com> (raw)
Add the __counted_by compiler attribute to the flexible array member
salt to improve access bounds-checking via CONFIG_UBSAN_BOUNDS and
CONFIG_FORTIFY_SOURCE.
Use struct_size_t() instead of manually calculating the struct's size.
Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
---
crypto/chacha20poly1305.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/crypto/chacha20poly1305.c b/crypto/chacha20poly1305.c
index 9e4651330852..b37f59a8280a 100644
--- a/crypto/chacha20poly1305.c
+++ b/crypto/chacha20poly1305.c
@@ -27,7 +27,7 @@ struct chachapoly_ctx {
struct crypto_ahash *poly;
/* key bytes we use for the ChaCha20 IV */
unsigned int saltlen;
- u8 salt[];
+ u8 salt[] __counted_by(saltlen);
};
struct poly_req {
@@ -611,8 +611,8 @@ static int chachapoly_create(struct crypto_template *tmpl, struct rtattr **tb,
poly->base.cra_priority) / 2;
inst->alg.base.cra_blocksize = 1;
inst->alg.base.cra_alignmask = chacha->base.cra_alignmask;
- inst->alg.base.cra_ctxsize = sizeof(struct chachapoly_ctx) +
- ctx->saltlen;
+ inst->alg.base.cra_ctxsize = struct_size_t(struct chachapoly_ctx, salt,
+ ctx->saltlen);
inst->alg.ivsize = ivsize;
inst->alg.chunksize = chacha->chunksize;
inst->alg.maxauthsize = POLY1305_DIGEST_SIZE;
--
2.45.2
next reply other threads:[~2024-08-05 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 17:52 Thorsten Blum [this message]
2024-08-05 17:59 ` [PATCH] crypto: chacha20poly1305 - Annotate struct chachapoly_ctx with __counted_by() Eric Biggers
2024-08-05 20:32 ` Thorsten Blum
2024-08-05 20:49 ` Kees Cook
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=20240805175237.63098-2-thorsten.blum@toblux.com \
--to=thorsten.blum@toblux.com \
--cc=davem@davemloft.net \
--cc=gustavoars@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kees@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@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