From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: horia.geanta@nxp.com, pankaj.gupta@nxp.com, gaurav.jain@nxp.com,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] crypto: caam - reject overlong RSA CRT parameters
Date: Sat, 03 Oct 2026 23:21:44 +0200 [thread overview]
Message-ID: <752d9ff313bb52a7f8d2295161c1d9a4@oss.cyber.gouv.fr> (raw)
In-Reply-To: <ao4xobfWhs5Ss8Uy@gondor.apana.org.au>
On 2026-08-26 02:21, Herbert Xu wrote:
> On Mon, Aug 10, 2026 at 03:40:24PM +0000, Jérémy Jean wrote:
>> caam_read_rsa_crt() right-aligns dP, dQ, and qInv in buffers sized
>> from the corresponding prime. rsa_parse_priv_key() only bounds these
>> integers against n, so a malformed key can provide, for example, a
>> two-byte dP with a one-byte p. dstlen - nbytes then underflows and
>> memcpy() writes outside the allocation during set_priv_key(). KASAN
>> reports a slab-out-of-bounds write in caam_read_rsa_crt().
>>
>> Reject empty or overlong CRT parameters after stripping leading zeros.
>> qInv is consumed by CAAM as a p-sized value, so size it from p rather
>> than q to match the DMA mapping in set_rsa_priv_f3_pdb(). Let the
>> top-level key cleanup handle partial form-3 allocations and return the
>> specific error to the caller.
>>
>> Also test nbytes before dereferencing it while stripping zeros, so an
>> all-zero integer does not read one byte beyond its input.
>>
>> Fixes: 4a651b122adb ("crypto: caam - add support for RSA key form 3")
>> Cc: stable@vger.kernel.org
>> Assisted-by: Codex:gpt-5
>> Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
>> ---
>> drivers/crypto/caam/caampkc.c | 69
>> +++++++++++++++--------------------
>> 1 file changed, 30 insertions(+), 39 deletions(-)
>
> Is this driver still maintained? If not let's just remove it.
>
> Thanks,
Hello,
I don't know for sure, but it is still getting fixed, e.g.,
https://lore.kernel.org/all/FF2F0DC4D3930E6A+20260923101457.204629-1-zhaojinming@uniontech.com/
Regards,
Jérémy
next prev parent reply other threads:[~2026-10-03 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 15:40 Jérémy Jean
2026-08-26 0:21 ` Herbert Xu
2026-10-03 21:21 ` Jérémy Jean [this message]
2026-10-08 8:36 ` Herbert Xu
2026-10-08 9:38 ` Jérémy Jean
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=752d9ff313bb52a7f8d2295161c1d9a4@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=stable@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
all inboxes | Powered by JetHome®