From: Jarkko Sakkinen <jarkko@kernel.org>
To: Guo Zihao <guozh23@xiaopeng.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] tpm: sessions: bound the primary public area by the response size
Date: Fri, 6 Nov 2026 17:21:13 +0200 [thread overview]
Message-ID: <au3waVnY6QA8TpPl@kernel.org> (raw)
In-Reply-To: <20261106014937.4127650-1-guozh23@xiaopeng.com>
On Fri, Nov 06, 2026 at 09:49:35AM +0800, Guo Zihao wrote:
> tpm2_parse_create_primary() reads the size of the TPM2B_PUBLIC area
> from the response and hashes it to compute the object name:
>
> len = tpm_buf_read_u16(buf, &offset_r);
> offset_t = offset_r;
> if (name) {
> /*
> * now we have the public area, compute the name of
> * the object
> */
> put_unaligned_be16(TPM_ALG_SHA256, name);
> sha256(&buf->data[offset_r], len, name + 2);
> }
>
> The length is only checked against the response later, after the
> hash has been taken. A TPM that reports a public area longer than
> what it actually sent makes the sha256() run past the end of the
> received data and hash whatever follows the response in the buffer.
>
> Check that the public area fits in the response before hashing it.
>
> Fixes: d2add27cf2b8 ("tpm: Add NULL primary creation")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
I think it is not a bug fix without a source.
I.e., unless this is TCG defined behavior, I'd not add fixes tag.
Br, Jarkko
prev parent reply other threads:[~2026-11-06 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 Guo Zihao
2026-11-06 1:49 ` [PATCH 2/2] tpm: sessions: bound the parameter decryption " Guo Zihao
2026-11-06 15:21 ` Jarkko Sakkinen
2026-11-06 15:21 ` Jarkko Sakkinen [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=au3waVnY6QA8TpPl@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ardb@kernel.org \
--cc=guozh23@xiaopeng.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@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
all inboxes | Powered by JetHome®