From: sashiko-bot@kernel.org
To: "Alex Ousherovitch" <aousherovitch@rambus.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 09/19] crypto: cmh - add SM4 skcipher/aead/cmac/xcbc
Date: Thu, 17 Sep 2026 23:10:50 +0000 [thread overview]
Message-ID: <20260917231050.B49791F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260917225929.2494111-10-aousherovitch@rambus.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] crypto: cmh: missing DoS limit check in cmh_sm4_mac_import allows memory exhaustion
--
commit 60aa3a7525d3c5b378e645a473550b644da1ca56
Author: Alex Ousherovitch <aousherovitch@rambus.com>
crypto: cmh - add SM4 skcipher/aead/cmac/xcbc
This commit registers SM4 skcipher, AEAD, and MAC (CMAC, XCBC) algorithms
using the CMH SM4 core. It implements various fallback mechanisms for empty
inputs and handles scatter-gather logic by linearizing memory buffers.
> diff --git a/drivers/crypto/cmh/cmh_sm4_cmac.c b/drivers/crypto/cmh/cmh_sm4_cmac.c
> new file mode 100644
> index 0000000000000..abeadce312c09
> --- /dev/null
> +++ b/drivers/crypto/cmh/cmh_sm4_cmac.c
[ ... ]
> +static int cmh_sm4_mac_import(struct ahash_request *req, const void *in)
> +{
> + struct crypto_ahash *tfm = crypto_ahash_reqtfm(req);
> + struct cmh_sm4_mac_tfm_ctx *tctx = crypto_ahash_ctx(tfm);
> + struct cmh_sm4_mac_reqctx *rctx = ahash_request_ctx(req);
> + const struct cmh_sm4_mac_export_state *state = in;
> + struct cmh_sm4_mac_chunk *chunk;
[ ... ]
> + if (state->total_len) {
> + chunk = kmalloc(sizeof(*chunk) + state->total_len,
> + req->base.flags & CRYPTO_TFM_REQ_MAY_SLEEP ?
> + GFP_KERNEL : GFP_ATOMIC);
> + if (!chunk)
> + return -ENOMEM;
> + chunk->len = state->total_len;
> + memcpy(chunk->data, state->data, state->total_len);
> + spin_lock_bh(&tctx->chunk_lock);
> + list_add_tail(&chunk->list, &rctx->chunks);
> + list_add_tail(&chunk->tfm_node, &tctx->all_chunks);
> + tctx->tfm_buffered += chunk->len;
> + spin_unlock_bh(&tctx->chunk_lock);
[Severity: High]
Does this code allow an unbounded memory allocation bypass?
When an AF_ALG socket is created for cmac(sm4) or xcbc(sm4), a user can write
some data so it gets buffered, and then repeatedly call accept() on the
socket. Each accept() clones the request, triggering a crypto_ahash_export
on the parent and a crypto_ahash_import on the child.
During cmh_sm4_mac_import(), the function allocates a new chunk for the
imported data and adds it to the per-tfm list tctx->all_chunks. However, it
does not check if the total buffered memory exceeds the
CMH_SM4_MAC_TFM_MAX_BUFFERED limit, unlike cmh_sm4_mac_update().
If the user closes the child socket, the allocated chunks are abandoned in
tctx->all_chunks. Repeating this indefinitely could exhaust kernel memory and
cause a denial of service.
> + rctx->total_len = state->total_len;
> + }
> + return 0;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917225929.2494111-1-aousherovitch@rambus.com?part=9
next prev parent reply other threads:[~2026-09-17 23:10 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 22:59 [PATCH v5 00/19] crypto: cmh - add Rambus CryptoManager Hub driver Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 01/19] dt-bindings: crypto: add Rambus CryptoManager Hub Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:08 ` sashiko-bot
2026-09-28 18:18 ` Rob Herring
2026-09-28 18:18 ` Rob Herring
2026-10-03 0:01 ` Ousherovitch, Alex
2026-10-03 0:01 ` Ousherovitch, Alex
2026-09-17 22:59 ` [PATCH v5 02/19] crypto: cmh - add core platform driver Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:17 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 03/19] crypto: cmh - add key provisioning and management Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:15 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 04/19] crypto: cmh - add SHA-2/SHA-3/SHAKE ahash Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:11 ` sashiko-bot
2026-09-23 5:47 ` Herbert Xu
2026-09-23 5:47 ` Herbert Xu
2026-09-23 20:50 ` Ousherovitch, Alex
2026-09-23 20:50 ` Ousherovitch, Alex
2026-09-28 5:17 ` Herbert Xu
2026-09-28 5:17 ` Herbert Xu
2026-10-05 17:04 ` Ousherovitch, Alex
2026-10-05 17:04 ` Ousherovitch, Alex
2026-10-05 22:31 ` Ousherovitch, Alex
2026-10-05 22:31 ` Ousherovitch, Alex
2026-10-08 8:20 ` Herbert Xu
2026-10-08 8:20 ` Herbert Xu
2026-10-08 18:19 ` Ousherovitch, Alex
2026-10-08 18:19 ` Ousherovitch, Alex
2026-09-17 22:59 ` [PATCH v5 05/19] crypto: cmh - add HMAC ahash Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:14 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 06/19] crypto: cmh - add CSHAKE/KMAC ahash Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:16 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 07/19] crypto: cmh - add SM3 ahash Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:12 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 08/19] crypto: cmh - add AES skcipher/aead/cmac Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:11 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 09/19] crypto: cmh - add SM4 skcipher/aead/cmac/xcbc Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:10 ` sashiko-bot [this message]
2026-09-17 22:59 ` [PATCH v5 10/19] crypto: cmh - add ChaCha20-Poly1305 Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:11 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 11/19] crypto: cmh - add DRBG hwrng Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:14 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 12/19] crypto: cmh - add RSA akcipher Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:10 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 13/19] crypto: cmh - add ECDSA/SM2 sig Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 14/19] crypto: cmh - add ECDH/X25519 kpp Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 15/19] crypto: cmh - add ML-KEM/ML-DSA (QSE) Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 16/19] crypto: cmh - add SLH-DSA/LMS/XMSS (HCQ) Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 17/19] Documentation: ioctl: add CMH ioctl documentation and register 'J' Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 23:17 ` sashiko-bot
2026-09-17 22:59 ` [PATCH v5 18/19] selftests: crypto: cmh - add kselftest for management ioctl Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-17 22:59 ` [PATCH v5 19/19] MAINTAINERS: add Rambus CryptoManager Hub (CMH) Alex Ousherovitch
2026-09-17 22:59 ` Alex Ousherovitch
2026-09-23 5:48 ` [PATCH v5 00/19] crypto: cmh - add Rambus CryptoManager Hub driver Herbert Xu
2026-09-23 5:48 ` Herbert Xu
2026-09-23 17:42 ` Ousherovitch, Alex
2026-09-23 17:42 ` Ousherovitch, Alex
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=20260917231050.B49791F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=aousherovitch@rambus.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.