From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-integrity@vger.kernel.org,
Jeremy Boone <Jeremy.Boone@nccgroup.trust>
Subject: Re: [PATCH 2/2] tpm drivers: fix potential buffer overruns caused by bit glitches on the bus
Date: Thu, 8 Feb 2018 15:37:00 +0200 [thread overview]
Message-ID: <20180208133700.dpewhiannolwpas2@linux.intel.com> (raw)
In-Reply-To: <1517592333.3137.20.camel@HansenPartnership.com>
On Fri, Feb 02, 2018 at 06:25:33PM +0100, James Bottomley wrote:
> 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/st33zp24/st33zp24.c | 4 ++--
> drivers/char/tpm/tpm_i2c_infineon.c | 5 +++--
> drivers/char/tpm/tpm_i2c_nuvoton.c | 5 +++--
> drivers/char/tpm/tpm_tis_core.c | 5 +++--
> 4 files changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/char/tpm/st33zp24/st33zp24.c b/drivers/char/tpm/st33zp24/st33zp24.c
> index 4d1dc8b46877..f95b9c75175b 100644
> --- a/drivers/char/tpm/st33zp24/st33zp24.c
> +++ b/drivers/char/tpm/st33zp24/st33zp24.c
> @@ -457,7 +457,7 @@ static int st33zp24_recv(struct tpm_chip *chip, unsigned char *buf,
> size_t count)
> {
> int size = 0;
> - int expected;
> + u32 expected;
>
> if (!chip)
> return -EBUSY;
> @@ -474,7 +474,7 @@ static int st33zp24_recv(struct tpm_chip *chip, unsigned char *buf,
> }
>
> expected = be32_to_cpu(*(__be32 *)(buf + 2));
> - if (expected > count) {
> + if (expected > count || expected < TPM_HEADER_SIZE) {
> size = -EIO;
> goto out;
> }
> diff --git a/drivers/char/tpm/tpm_i2c_infineon.c b/drivers/char/tpm/tpm_i2c_infineon.c
> index 79d6bbb58e39..d5b44cadac56 100644
> --- a/drivers/char/tpm/tpm_i2c_infineon.c
> +++ b/drivers/char/tpm/tpm_i2c_infineon.c
> @@ -473,7 +473,8 @@ static int recv_data(struct tpm_chip *chip, u8 *buf, size_t count)
> static int tpm_tis_i2c_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> {
> int size = 0;
> - int expected, status;
> + int status;
> + u32 expected;
>
> if (count < TPM_HEADER_SIZE) {
> size = -EIO;
> @@ -488,7 +489,7 @@ static int tpm_tis_i2c_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> }
>
> expected = be32_to_cpu(*(__be32 *)(buf + 2));
> - if ((size_t) expected > count) {
> + if (((size_t) expected > count) || (expected < TPM_HEADER_SIZE)) {
> size = -EIO;
> goto out;
> }
> 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;
> diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
> index fdde971bc810..7561922bc8f8 100644
> --- a/drivers/char/tpm/tpm_tis_core.c
> +++ b/drivers/char/tpm/tpm_tis_core.c
> @@ -202,7 +202,8 @@ static int tpm_tis_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> {
> struct tpm_tis_data *priv = dev_get_drvdata(&chip->dev);
> int size = 0;
> - int expected, status;
> + int status;
> + u32 expected;
>
> if (count < TPM_HEADER_SIZE) {
> size = -EIO;
> @@ -217,7 +218,7 @@ static int tpm_tis_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> }
>
> expected = be32_to_cpu(*(__be32 *) (buf + 2));
> - if (expected > count) {
> + if (expected > count || expected < TPM_HEADER_SIZE) {
> size = -EIO;
> goto out;
> }
> --
> 2.12.3
LGTM but should be split into four commits.
/Jarkko
next prev parent reply other threads:[~2018-02-08 13:37 UTC|newest]
Thread overview: 9+ 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 ` [PATCH 1/2] tpm: fix potential buffer overruns caused by bit glitches on the bus James Bottomley
2018-02-08 13:34 ` 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 [this message]
2018-02-02 18:48 ` [PATCH 0/2] Fix kernel buffer overruns caused by bit flips Jason Gunthorpe
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=20180208133700.dpewhiannolwpas2@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).