From: Stefano Garzarella <sgarzare@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-integrity@vger.kernel.org, stable@vger.kernel.org,
co+6a581c4284f721d4@bugs.sh,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Mimi Zohar <zohar@linux.ibm.com>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Jonathan McDowell <noodles@meta.com>,
Ross Philipson <ross.philipson@gmail.com>,
Stefan Berger <stefanb@linux.ibm.com>,
Srish Srinivasan <ssrish@linux.ibm.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: trusted: Fix tpm2_load_cmd() boundary check
Date: Wed, 2 Sep 2026 11:24:16 +0200 [thread overview]
Message-ID: <apfoKo-BdwaLXtkT@sgarzare-redhat> (raw)
In-Reply-To: <20260901205809.2028454-1-jarkko@kernel.org>
On Tue, Sep 01, 2026 at 11:58:06PM +0300, Jarkko Sakkinen wrote:
>tpm2_load_cmd() does boundary checks against the ASN.1 size i.e.,
>payload->blob_len. Address this by passing the decoded blob size to
>tpm2_load_cmd(), and use it for the boundary checks.
>
>Cc: stable@vger.kernel.org # v5.13+
>Fixes: f2219745250f ("security: keys: trusted: use ASN.1 TPM2 key format for the blobs")
>Reported-by: co+6a581c4284f721d4@bugs.sh
>Closes: https://bugs.sh/b/6a581c4284f721d4/
>Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
>---
> security/keys/trusted-keys/trusted_tpm2.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
>diff --git a/security/keys/trusted-keys/trusted_tpm2.c b/security/keys/trusted-keys/trusted_tpm2.c
>index 67225dd562a9..01f18bb37047 100644
>--- a/security/keys/trusted-keys/trusted_tpm2.c
>+++ b/security/keys/trusted-keys/trusted_tpm2.c
>@@ -99,7 +99,7 @@ struct tpm2_key_context {
>
> static int tpm2_key_decode(struct trusted_key_payload *payload,
> struct trusted_key_options *options,
>- u8 **buf)
>+ u8 **buf, unsigned int *blob_len)
> {
> int ret;
> struct tpm2_key_context ctx;
>@@ -120,6 +120,7 @@ static int tpm2_key_decode(struct trusted_key_payload *payload,
blob = kmalloc(ctx.priv_len + ctx.pub_len + 4, GFP_KERNEL);
Pre-existing, but is `+ 4` here useless?
I'm not asking to fix here, just noticed while reviewing.
Maybe we can set *blob_len earlier and use it also in the kmalloc().
Not a strong opinion, that said this LGTM:
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
if (!blob)
> return -ENOMEM;
>
> *buf = blob;
>+ *blob_len = ctx.priv_len + ctx.pub_len;
> options->keyhandle = ctx.parent;
>
> memcpy(blob, ctx.priv, ctx.priv_len);
>@@ -384,10 +385,11 @@ static int tpm2_load_cmd(struct tpm_chip *chip,
> int rc;
> u32 attrs;
>
>- rc = tpm2_key_decode(payload, options, &blob);
>+ rc = tpm2_key_decode(payload, options, &blob, &blob_len);
> if (rc) {
> /* old form */
> blob = payload->blob;
>+ blob_len = payload->blob_len;
> payload->old_format = 1;
> } else {
> /* Bind for cleanup: */
>@@ -399,17 +401,17 @@ static int tpm2_load_cmd(struct tpm_chip *chip,
> return -EINVAL;
>
> /* must be big enough for at least the two be16 size counts */
>- if (payload->blob_len < 4)
>+ if (blob_len < 4)
> return -EINVAL;
>
> private_len = get_unaligned_be16(blob);
>
> /* must be big enough for following public_len */
>- if (private_len + 2 + 2 > (payload->blob_len))
>+ if (private_len + 2 + 2 > blob_len)
> return -E2BIG;
>
> public_len = get_unaligned_be16(blob + 2 + private_len);
>- if (private_len + 2 + public_len + 2 > payload->blob_len)
>+ if (private_len + 2 + public_len + 2 > blob_len)
> return -E2BIG;
>
> pub = blob + 2 + private_len + 2;
>--
>2.47.3
>
next prev parent reply other threads:[~2026-09-02 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 20:58 [PATCH] KEYS: trusted: Fix tpm2_load_cmd() boundary check Jarkko Sakkinen
2026-09-02 9:24 ` Stefano Garzarella [this message]
2026-09-03 9:31 ` Srish Srinivasan
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=apfoKo-BdwaLXtkT@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=co+6a581c4284f721d4@bugs.sh \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=noodles@meta.com \
--cc=paul@paul-moore.com \
--cc=ross.philipson@gmail.com \
--cc=serge@hallyn.com \
--cc=ssrish@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.com \
/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