From: Guo Zihao <guozh23@xiaopeng.com>
To: Peter Huewe <peterhuewe@gmx.de>, Jarkko Sakkinen <jarkko@kernel.org>
Cc: 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
Subject: [PATCH v2] tpm: ibmvtpm: check the response size against the buffer size
Date: Mon, 9 Nov 2026 09:49:57 +0800 [thread overview]
Message-ID: <20261109014957.2777790-1-guozh23@xiaopeng.com> (raw)
In-Reply-To: <au3w4NDX1Uqz-iqd@kernel.org>
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.
Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
---
v2: Drop the Fixes and Cc: stable tags, as suggested by Jarkko
Sakkinen: a hypervisor reporting an oversized response is not
known to violate the architecture, so this is hardening rather
than a bug fix. No code changes.
drivers/char/tpm/tpm_ibmvtpm.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/char/tpm/tpm_ibmvtpm.c b/drivers/char/tpm/tpm_ibmvtpm.c
index 6fb4d30eb6f6..bfef4bc14767 100644
--- a/drivers/char/tpm/tpm_ibmvtpm.c
+++ b/drivers/char/tpm/tpm_ibmvtpm.c
@@ -121,6 +121,13 @@ static int tpm_ibmvtpm_recv(struct tpm_chip *chip, u8 *buf, size_t count)
return -EIO;
}
+ if (len > ibmvtpm->rtce_size) {
+ dev_err(ibmvtpm->dev,
+ "Invalid size in recv: res_len=%d, rtce_size=%d\n",
+ len, ibmvtpm->rtce_size);
+ return -EIO;
+ }
+
spin_lock(&ibmvtpm->rtce_lock);
memcpy((void *)buf, (void *)ibmvtpm->rtce_buf, len);
memset(ibmvtpm->rtce_buf, 0, len);
--
2.50.1
prev parent reply other threads:[~2026-11-09 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 [PATCH] " Guo Zihao
2026-11-06 15:23 ` Jarkko Sakkinen
2026-11-09 1:49 ` Guo Zihao [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=20261109014957.2777790-1-guozh23@xiaopeng.com \
--to=guozh23@xiaopeng.com \
--cc=adlai@linux.vnet.ibm.com \
--cc=jarkko@kernel.org \
--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 \
/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®