From: Sudhakar Kuppusamy <sudhakar@linux.ibm.com>
To: Sanket Sharma <sanketsharmacsec@gmail.com>
Cc: jarkko@kernel.org, gregkh@linuxfoundation.org,
"James.Bottomley@hansenpartnership.com"
<James.Bottomley@HansenPartnership.com>,
zohar@linux.ibm.com, dhowells@redhat.com,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, security@kernel.org, w@1wt.eu
Subject: Re: [PATCH v2 1/2] keys: trusted: tpm1: add bounds check in tpm_seal() before memcpy
Date: Wed, 26 Aug 2026 22:14:46 +0530 [thread overview]
Message-ID: <284F8B1D-F60A-4BBB-80B3-D2814A165DC1@linux.ibm.com> (raw)
In-Reply-To: <20260826080405.255083-1-sanketsharmacsec@gmail.com>
> On 26 Aug 2026, at 1:34 PM, Sanket Sharma <sanketsharmacsec@gmail.com> wrote:
>
> tpm_seal() computes storedsize from TPM response fields and passes
> it directly to memcpy() into a MAX_BLOB_SIZE buffer without bounds
> validation. A forged TPM response can set storedsize to 4086,
> overflowing the 512-byte blob by 3574 bytes into adjacent slab
> objects.
>
> Add a check that storedsize does not exceed MAX_BLOB_SIZE before
> the memcpy, returning -EINVAL on oversized responses.
>
> Signed-off-by: Sanket Sharma <sanketsharmacsec@gmail.com>
Reviewed-by: Sudhakar Kuppusamy <sudhakar@linux.ibm.com>
Thanks,
Sudhakar
> ---
> security/keys/trusted-keys/trusted_tpm1.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/security/keys/trusted-keys/trusted_tpm1.c b/security/keys/trusted-keys/trusted_tpm1.c
> index 8f57c6111..d47cb7108 100644
> --- a/security/keys/trusted-keys/trusted_tpm1.c
> +++ b/security/keys/trusted-keys/trusted_tpm1.c
> @@ -531,6 +531,10 @@ static int tpm_seal(struct tpm_buf *tb, uint16_t keytype,
>
> /* copy the returned blob to caller */
> if (!ret) {
> + if (storedsize > MAX_BLOB_SIZE) {
> + ret = -EINVAL;
> + goto out;
> + }
> memcpy(blob, tb->data + TPM_DATA_OFFSET, storedsize);
> *bloblen = storedsize;
> }
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-08-26 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 18:29 [PATCH " sn0x-sharma
2026-08-25 18:29 ` [PATCH 2/2] keys: trusted: tpm1: reject unauthenticated response tag in TSS_checkhmac1/2 sn0x-sharma
2026-08-28 1:44 ` Jarkko Sakkinen
2026-08-26 6:18 ` [PATCH 1/2] keys: trusted: tpm1: add bounds check in tpm_seal() before memcpy Greg KH
2026-08-28 1:46 ` Jarkko Sakkinen
[not found] ` <CAEb43b2C_eyR8ncUbJ+3MsT3ap-tB3_O0Mbaqgy1ncXwZAd_Yw@mail.gmail.com>
2026-08-28 7:36 ` Greg KH
[not found] ` <CAEb43b0bc7rNvrpLmjF-9HPEfUcOdTKsUC68vzh+JfDf7E+OcA@mail.gmail.com>
2026-09-01 12:36 ` Jarkko Sakkinen
2026-08-26 8:04 ` [PATCH v2 " Sanket Sharma
2026-08-26 8:04 ` [PATCH v2 2/2] keys: trusted: tpm1: reject unauthenticated response tag in TSS_checkhmac1/2 Sanket Sharma
2026-08-26 16:47 ` Sudhakar Kuppusamy
2026-08-26 16:44 ` Sudhakar Kuppusamy [this message]
2026-08-26 17:06 ` [PATCH v3 1/2] keys: trusted: tpm1: add bounds check in tpm_seal() before memcpy Sanket Sharma
2026-08-26 17:07 ` [PATCH v3 2/2] keys: trusted: tpm1: reject unauthenticated response tag in TSS_checkhmac1/2 Sanket Sharma
2026-08-28 1:48 ` Jarkko Sakkinen
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=284F8B1D-F60A-4BBB-80B3-D2814A165DC1@linux.ibm.com \
--to=sudhakar@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanketsharmacsec@gmail.com \
--cc=security@kernel.org \
--cc=w@1wt.eu \
--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
all inboxes | Powered by JetHome®