From: Vasily Gorbik <gor@linux.ibm.com>
To: Holger Dengler <dengler@linux.ibm.com>
Cc: freude@linux.ibm.com, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
ifranzki@linux.ibm.com
Subject: Re: [PATCH v1 0/2] s390/zcrypt: Validate length in CCA key requests
Date: Wed, 29 Jul 2026 15:30:50 +0200 [thread overview]
Message-ID: <ttixuve@ub.hpns> (raw)
In-Reply-To: <20260729093616.4184642-1-dengler@linux.ibm.com>
On Wed, Jul 29, 2026 at 11:36:14AM +0200, Holger Dengler wrote:
> The series contains two missing length field validations for requests
> with CCA AES cipher keys and CCA ECC private keys. In both cases, the
> length information is used to copy the payload to the request block
> without checking the available space. Malformed requests can so cause
> out-of-band writes on the heap.
>
> This series applies on top of Linus' master branch.
>
> Holger Dengler (2):
> s390/zcrypt: Validate length for CCA AES cipher key requests
> s390/zcrypt: Validate length for CCA ECC private key requests
>
> drivers/s390/crypto/zcrypt_ccamisc.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied, thank you!
prev parent reply other threads:[~2026-07-29 13:31 UTC|newest]
Thread overview: 10+ 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
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
2026-07-29 13:30 ` Vasily Gorbik [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=ttixuve@ub.hpns \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=ifranzki@linux.ibm.com \
--cc=linux-s390@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