From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-integrity@vger.kernel.org
Cc: Jeremy Boone <Jeremy.Boone@nccgroup.trust>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: [PATCH v2 4/5] tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on the bus
Date: Thu, 08 Feb 2018 12:31:16 -0800 [thread overview]
Message-ID: <1518121876.21828.16.camel@HansenPartnership.com> (raw)
In-Reply-To: <1518121576.21828.10.camel@HansenPartnership.com>
From: Jeremy Boone <jeremy.boone@nccgroup.trust>
Discrete TPMs are often connected over slow serial buses which, on
some platforms, can have glitches causing bit flips. In all the
driver _recv() functions, we need to use a u32 to unmarshal the
response size, otherwise a bit flip of the 31st bit would cause the
expected variable to go negative, which would then try to read a huge
amount of data. Also sanity check that the expected amount of data is
large enough for the TPM header.
Signed-off-by: Jeremy Boone <jeremy.boone@nccgroup.trust>
Cc: stable@vger.kernel.org
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
---
drivers/char/tpm/tpm_i2c_nuvoton.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/char/tpm/tpm_i2c_nuvoton.c b/drivers/char/tpm/tpm_i2c_nuvoton.c
index c6428771841f..17cf7af9a2c5 100644
--- a/drivers/char/tpm/tpm_i2c_nuvoton.c
+++ b/drivers/char/tpm/tpm_i2c_nuvoton.c
@@ -281,7 +281,8 @@ static int i2c_nuvoton_recv(struct tpm_chip *chip, u8 *buf, size_t count)
struct device *dev = chip->dev.parent;
struct i2c_client *client = to_i2c_client(dev);
s32 rc;
- int expected, status, burst_count, retries, size = 0;
+ int status, burst_count, retries, size = 0;
+ u32 expected;
if (count < TPM_HEADER_SIZE) {
i2c_nuvoton_ready(chip); /* return to idle */
@@ -323,7 +324,7 @@ static int i2c_nuvoton_recv(struct tpm_chip *chip, u8 *buf, size_t count)
* to machine native
*/
expected = be32_to_cpu(*(__be32 *) (buf + 2));
- if (expected > count) {
+ if (expected > count || expected < size) {
dev_err(dev, "%s() expected > count\n", __func__);
size = -EIO;
continue;
--
2.12.3
next prev parent reply other threads:[~2018-02-08 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 20:26 [PATCH v2 0/2] Fix kernel buffer overruns caused by bit flips James Bottomley
2018-02-08 20:29 ` [PATCH v2 2/5] tpm: st33zp24: fix potential buffer overruns caused by bit glitches on the bus James Bottomley
2018-02-08 20:30 ` [PATCH v2 3/5] tpm_i2c_infineon: " James Bottomley
2018-02-08 20:31 ` James Bottomley [this message]
2018-02-08 20:32 ` [PATCH v2 5/5] tpm_tis: " James Bottomley
2018-02-09 17:13 ` [PATCH v2 0/2] Fix kernel buffer overruns caused by bit flips Jarkko Sakkinen
2018-02-09 17:33 ` James Bottomley
2018-02-14 11:44 ` Jarkko Sakkinen
2018-02-14 13:04 ` 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=1518121876.21828.16.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Jeremy.Boone@nccgroup.trust \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@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