Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Holger Dengler" <dengler@linux.ibm.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v1 1/2] s390/zcrypt: Validate length for CCA AES cipher key requests
Date: Wed, 29 Jul 2026 09:58:20 +0000	[thread overview]
Message-ID: <20260729095821.1DE5D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729093616.4184642-2-dengler@linux.ibm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [Critical] Heap buffer overflow in `cca_ecc2protkey` when copying a user-provided ECC key token into a fixed-size buffer.
--

--- Patch [1]: [PATCH v1 1/2] s390/zcrypt: Validate length for CCA AES cipher key requests ---
commit 7b35c8aa05e7fb7c7837b88e5f3b7fc85f721c98
Author: Holger Dengler <dengler@linux.ibm.com>

s390/zcrypt: Validate length for CCA AES cipher key requests

This commit adds a bounds check in cca_cipher2protkey() to ensure the copy
length derived from the key token does not exceed the available space in the
CPRB parameter block. If the length is too large, the request is rejected
early with -EINVAL.

> diff --git a/drivers/s390/crypto/zcrypt_ccamisc.c b/drivers/s390/crypto/zcrypt_ccamisc.c
> index 84936a795b956..db6a4211a97e0 100644
> --- a/drivers/s390/crypto/zcrypt_ccamisc.c
> +++ b/drivers/s390/crypto/zcrypt_ccamisc.c
> @@ -1261,6 +1261,9 @@ int cca_cipher2protkey(u16 cardnr, u16 domain, const u8 *ckey,
>  	} __packed * prepparm;
>  	int keytoklen = ((struct cipherkeytoken *)ckey)->len;
>  
> +	if (keytoklen > PARMBSIZE - sizeof(struct aureqparm))
> +		return -EINVAL;
> +

[Severity: Critical]
This is a pre-existing issue, but does a similar heap buffer overflow exist in
cca_ecc2protkey()?

It appears cca_ecc2protkey() also copies a user-provided ECC key token into a
fixed-size buffer without a similar bounds check. A user with access to
/dev/pkey could call the PKEY_KBLOB2PROTK2 ioctl, passing an
eccprivkeytoken with a large len field.

This would be passed down through cca_key2protkey() to cca_ecc2protkey(),
where it allocates a 512-byte parameter block via
alloc_and_prep_cprbmem() and copies the token:

drivers/s390/crypto/zcrypt_ccamisc.c:cca_ecc2protkey() {
    ...
	int keylen = ((struct eccprivkeytoken *)key)->len;

	/* get already prepared memory for 2 cprbs with param block each */
	rc = alloc_and_prep_cprbmem(PARMBSIZE, &mem,
				    &preqcblk, &prepcblk, xflags);
    ...
	/* kb, cca token */
	preqparm->kb.len = keylen + 3 * sizeof(uint16_t);
	preqparm->kb.cca_key_token_len = keylen + 2 * sizeof(uint16_t);
	memcpy(preqparm->kb.cca_key_token, key, keylen);
    ...
}

Since the parameter block header consumes 90 bytes, any keylen > 422 bytes
could overflow the allocated memory. Is a similar check needed there?

>  	/* get already prepared memory for 2 cprbs with param block each */
>  	rc = alloc_and_prep_cprbmem(PARMBSIZE, &mem,
>  				    &preqcblk, &prepcblk, xflags);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260729093616.4184642-1-dengler@linux.ibm.com?part=1

  reply	other threads:[~2026-07-29  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  9:36 [PATCH v1 0/2] s390/zcrypt: Validate length in CCA key requests Holger Dengler
2026-07-29  9:36 ` [PATCH v1 1/2] s390/zcrypt: Validate length for CCA AES cipher " Holger Dengler
2026-07-29  9:58   ` sashiko-bot [this message]
2026-07-29 11:01     ` Holger Dengler
2026-07-29 10:10   ` Harald Freudenberger
2026-07-29  9:36 ` [PATCH v1 2/2] s390/zcrypt: Validate length for CCA ECC private " Holger Dengler
2026-07-29 10:10   ` Harald Freudenberger
2026-07-29 10:16   ` sashiko-bot
2026-07-29 11:22     ` Holger Dengler

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=20260729095821.1DE5D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=dengler@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox