From: Finn Callies <fcallies@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>,
dengler@linux.ibm.com, ifranzki@linux.ibm.com
Cc: linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH v1 1/1] s390/zcrypt: Fix uninitialized padding in CRT key structure
Date: Wed, 26 Aug 2026 06:34:13 +0200 [thread overview]
Message-ID: <fade6367-b9ce-4944-932c-a1b19cb84a73@linux.ibm.com> (raw)
In-Reply-To: <20260825160154.106501-2-freude@linux.ibm.com>
On 25.08.26 18:01, Harald Freudenberger wrote:
> The zcrypt_type6_crt_key() function leaves padding bytes uninitialized
> between key components and the modulus in the CCA CRT key token. These
> padding bytes are sent to the crypto card, potentially leaking kernel
> memory contents.
>
> The initial memset() only zeros fixed structure fields, not the
> flexible array member key_parts[] where the padding resides. While key
> components are properly copied from userspace, the calculated pad_len
> bytes between them remain uninitialized.
>
> Fix by explicitly zeroing the padding bytes after copying the CRT key
> components.
>
> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
> ---
> drivers/s390/crypto/zcrypt_cca_key.h | 1 +
> 1 file changed, 1 insertion(+)
>
[ snip ]
Reviewed-by: Finn Callies <fcallies@linux.ibm.com>
next prev parent reply other threads:[~2026-08-26 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 16:01 [PATCH v1 0/1] zcrypt crt and me fixes Harald Freudenberger
2026-08-25 16:01 ` [PATCH v1 1/1] s390/zcrypt: Fix uninitialized padding in CRT key structure Harald Freudenberger
2026-08-25 16:17 ` sashiko-bot
2026-08-26 4:34 ` Finn Callies [this message]
2026-08-26 23:05 ` [PATCH v1 0/1] zcrypt crt and me fixes Vasily Gorbik
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=fade6367-b9ce-4944-932c-a1b19cb84a73@linux.ibm.com \
--to=fcallies@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@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