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
Subject: Re: [PATCH v2 2/2] tpm: sessions: bound the parameter decryption by the response size
Date: Mon, 9 Nov 2026 16:51:35 +0200 [thread overview]
Message-ID: <avHd9w2d_nS6pdml@kernel.org> (raw)
In-Reply-To: <20261109014955.2777635-2-guozh23@xiaopeng.com>
On Mon, Nov 09, 2026 at 09:49:55AM +0800, Guo Zihao wrote:
> tpm_buf_check_hmac_response() decrypts the parameter area of a
> response for sessions with TPM2_SA_ENCRYPT set:
>
> len = tpm_buf_read_u16(buf, &offset_p);
> aes_prepareenckey(&auth->aes_key, auth->scratch, AES_KEY_BYTES);
> aescfb_decrypt(&auth->aes_key, &buf->data[offset_p],
> &buf->data[offset_p], len,
> auth->scratch + AES_KEY_BYTES);
>
> The length is read from the response itself and never checked
> against the buffer: every other size taken from a session response
> is compared to tpm_buf_length(), but not this one. A TPM that
> reports an oversized parameter area makes aescfb_decrypt() walk
> past the end of the buffer, and since the decryption is done in
> place, this both reads and writes whatever follows the received
> data.
>
> Check that the encrypted parameters fit in the response before
> decrypting them.
>
> Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
> ---
>
> v2: Drop the Fixes and Cc: stable tags, as suggested by Jarkko
> Sakkinen: a TPM reporting an oversized parameter area is not known
> to violate the TCG specification, so this is hardening rather
> than a bug fix. No code changes.
>
> drivers/char/tpm/tpm2-sessions.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/char/tpm/tpm2-sessions.c b/drivers/char/tpm/tpm2-sessions.c
> index e140079dbc13..59c7fdc0c88e 100644
> --- a/drivers/char/tpm/tpm2-sessions.c
> +++ b/drivers/char/tpm/tpm2-sessions.c
> @@ -872,6 +872,10 @@ int tpm_buf_check_hmac_response(struct tpm_chip *chip, struct tpm_buf *buf,
> auth->scratch);
>
> len = tpm_buf_read_u16(buf, &offset_p);
> + if (offset_p + len > tpm_buf_length(buf)) {
> + rc = -EINVAL;
> + goto out;
> + }
> aes_prepareenckey(&auth->aes_key, auth->scratch, AES_KEY_BYTES);
> aescfb_decrypt(&auth->aes_key, &buf->data[offset_p],
> &buf->data[offset_p], len,
> --
> 2.50.1
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Br, Jarkko
next prev parent reply other threads:[~2026-11-09 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 [PATCH 1/2] tpm: sessions: bound the primary public area " 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 ` [PATCH 1/2] tpm: sessions: bound the primary public area " Jarkko Sakkinen
2026-11-09 1:49 ` [PATCH v2 " Guo Zihao
2026-11-09 1:49 ` [PATCH v2 2/2] tpm: sessions: bound the parameter decryption " Guo Zihao
2026-11-09 14:51 ` Jarkko Sakkinen [this message]
2026-11-09 14:50 ` [PATCH v2 1/2] tpm: sessions: bound the primary public area " 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=avHd9w2d_nS6pdml@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 \
/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®