The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Ruoyu Wang <ruoyuw560@gmail.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tpm: st33zp24: Return zero on status read failure
Date: Fri, 21 Aug 2026 04:07:45 +0300	[thread overview]
Message-ID: <aoek4RzTzKQeswUd@kernel.org> (raw)
In-Reply-To: <20260813153032.3951878-1-ruoyuw560@gmail.com>

On Thu, Aug 13, 2026 at 11:30:31PM +0800, Ruoyu Wang wrote:
> st33zp24_status() ignores the result of the transport read and returns
> data even when no byte was received. The I2C transport, for example,
> skips i2c_master_recv() when the register-select write is short or fails,
> leaving data uninitialized. The resulting stack value can be interpreted
> as TPM_STS flags and let status checks complete spuriously.
> 
> The status callback cannot propagate a transport error. Return zero
> unless recv() reports exactly one byte. With no status bits set, callers
> retry or take their existing timeout or error path instead of acting on
> an invalid status value.
> 
> This issue was found by a static analysis checker and confirmed by manual
> source review.
> 
> Fixes: 251a7b08213a ("TPM: STMicroelectronics ST33 I2C KERNEL 3.x")
> Signed-off-by: Ruoyu Wang <ruoyuw560@gmail.com>
> ---
>  drivers/char/tpm/st33zp24/st33zp24.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/char/tpm/st33zp24/st33zp24.c b/drivers/char/tpm/st33zp24/st33zp24.c
> index e2b7451ea7ccd3..898e8d01d26698 100644
> --- a/drivers/char/tpm/st33zp24/st33zp24.c
> +++ b/drivers/char/tpm/st33zp24/st33zp24.c
> @@ -93,7 +93,9 @@ static u8 st33zp24_status(struct tpm_chip *chip)
>  	struct st33zp24_dev *tpm_dev = dev_get_drvdata(&chip->dev);
>  	u8 data;
>  
> -	tpm_dev->ops->recv(tpm_dev->phy_id, TPM_STS, &data, 1);
> +	if (tpm_dev->ops->recv(tpm_dev->phy_id, TPM_STS, &data, 1) != 1)
> +		return 0;
> +
>  	return data;
>  }
>  
> -- 
> 2.51.0
> 

Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>

thanks

BR, Jarkko

      parent reply	other threads:[~2026-08-21  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 15:30 [PATCH 1/2] tpm: st33zp24: Return zero on status read failure Ruoyu Wang
2026-08-13 15:30 ` [PATCH 2/2] tpm: st33zp24: Validate locality read result Ruoyu Wang
2026-08-21  1:12   ` Jarkko Sakkinen
2026-08-21  1:07 ` 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=aoek4RzTzKQeswUd@kernel.org \
    --to=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=ruoyuw560@gmail.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