From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-integrity@vger.kernel.org
Cc: Jeremy Boone <Jeremy.Boone@nccgroup.trust>
Subject: [PATCH 1/2] tpm: fix potential buffer overruns caused by bit glitches on the bus
Date: Fri, 02 Feb 2018 18:24:38 +0100 [thread overview]
Message-ID: <1517592278.3137.19.camel@HansenPartnership.com> (raw)
In-Reply-To: <1517592221.3137.18.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. If a bit does
flip it could cause an overrun if it's in one of the size parameters,
so sanity check that we're not overrunning the provided buffer when
doing a memcpy().
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-interface.c | 1 +
drivers/char/tpm/tpm2-cmd.c | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/drivers/char/tpm/tpm-interface.c b/drivers/char/tpm/tpm-interface.c
index 1d6729be4cd6..e99f4f71c74f 100644
--- a/drivers/char/tpm/tpm-interface.c
+++ b/drivers/char/tpm/tpm-interface.c
@@ -1228,6 +1228,7 @@ int tpm_get_random(u32 chip_num, u8 *out, size_t max)
break;
recd = be32_to_cpu(tpm_cmd.params.getrandom_out.rng_data_len);
+ recd = min_t(u32, recd, num_bytes);
rlength = be32_to_cpu(tpm_cmd.header.out.length);
if (rlength < offsetof(struct tpm_getrandom_out, rng_data) +
diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm/tpm2-cmd.c
index f40d20671a78..f6be08483ae6 100644
--- a/drivers/char/tpm/tpm2-cmd.c
+++ b/drivers/char/tpm/tpm2-cmd.c
@@ -683,6 +683,10 @@ static int tpm2_unseal_cmd(struct tpm_chip *chip,
if (!rc) {
data_len = be16_to_cpup(
(__be16 *) &buf.data[TPM_HEADER_SIZE + 4]);
+ if (data_len < MIN_KEY_SIZE || data_len > MAX_KEY_SIZE + 1) {
+ rc = -EFAULT;
+ goto out;
+ }
rlength = be32_to_cpu(((struct tpm2_cmd *)&buf)
->header.out.length);
--
2.12.3
next prev parent reply other threads:[~2018-02-02 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 17:23 [PATCH 0/2] Fix kernel buffer overruns caused by bit flips James Bottomley
2018-02-02 17:24 ` James Bottomley [this message]
2018-02-08 13:34 ` [PATCH 1/2] tpm: fix potential buffer overruns caused by bit glitches on the bus Jarkko Sakkinen
2018-02-08 15:56 ` EXTERNAL: " Jeremy Boone
2018-02-08 17:07 ` James Bottomley
2018-02-09 16:14 ` Jarkko Sakkinen
2018-02-02 17:25 ` [PATCH 2/2] tpm drivers: " James Bottomley
2018-02-08 13:37 ` Jarkko Sakkinen
2018-02-02 18:48 ` [PATCH 0/2] Fix kernel buffer overruns caused by bit flips Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2018-03-21 8:48 [PATCH 1/2] tpm: fix potential buffer overruns caused by bit glitches on the bus 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=1517592278.3137.19.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Jeremy.Boone@nccgroup.trust \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.