From: Jarkko Sakkinen <jarkko@kernel.org>
To: Guo Zihao <guozh23@xiaopeng.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Ashley Lai <adlai@linux.vnet.ibm.com>,
Kent Yoder <key@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] tpm: ibmvtpm: check the response size against the buffer size
Date: Fri, 6 Nov 2026 17:23:12 +0200 [thread overview]
Message-ID: <au3w4NDX1Uqz-iqd@kernel.org> (raw)
In-Reply-To: <20261106014946.4128696-1-guozh23@xiaopeng.com>
On Fri, Nov 06, 2026 at 09:49:46AM +0800, Guo Zihao wrote:
> The send path validates the transfer size against the size of the
> RTCE buffer:
>
> if (count > ibmvtpm->rtce_size) {
> dev_err(ibmvtpm->dev,
> "Invalid size in send: count=%zd, rtce_size=%d\n",
> count, ibmvtpm->rtce_size);
> return -EIO;
> }
>
> The receive path has no such check: the response length is whatever
> the hypervisor reported in the completion CRQ, and it is only
> compared against the size the caller asked for before being used to
> copy and clear the RTCE buffer:
>
> len = ibmvtpm->res_len;
>
> if (count < len) {
> ...
> return -EIO;
> }
>
> spin_lock(&ibmvtpm->rtce_lock);
> memcpy((void *)buf, (void *)ibmvtpm->rtce_buf, len);
> memset(ibmvtpm->rtce_buf, 0, len);
>
> A response length larger than the RTCE buffer makes the memcpy read
> past the buffer and the memset clear past it.
>
> Reject a response that does not fit in the RTCE buffer, mirroring
> the check the send path already performs.
>
> Fixes: 132f76294744 ("drivers/char/tpm: Add new device driver to support IBM vTPM")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
> ---
Ditto. I.e, I'm not sure if this is a bug fix or just better validation
for failing components.
Br, Jarkko
prev parent reply other threads:[~2026-11-06 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 Guo Zihao
2026-11-06 15:23 ` 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=au3w4NDX1Uqz-iqd@kernel.org \
--to=jarkko@kernel.org \
--cc=adlai@linux.vnet.ibm.com \
--cc=guozh23@xiaopeng.com \
--cc=jgg@ziepe.ca \
--cc=key@linux.vnet.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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®