public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	jmorris@namei.org
Cc: linux-integrity@vger.kernel.org,
	Jeremy Boone <Jeremy.Boone@nccgroup.trust>
Subject: Re: [PATCH v2 0/2] Fix kernel buffer overruns caused by bit flips
Date: Fri, 9 Feb 2018 19:13:24 +0200	[thread overview]
Message-ID: <20180209171324.ciuw6jadxnoyxty7@linux.intel.com> (raw)
In-Reply-To: <1518121576.21828.10.camel@HansenPartnership.com>

On Thu, Feb 08, 2018 at 12:26:16PM -0800, James Bottomley wrote:
> If a TPM is attached to a system via a serial bus on a platform that
> suffers bit flips, we can get back dangerously wrong data.  This patch
> series aims never to do a direct copy into a kernel buffer based on an
> unchecked size value returned from the TPM.
> 
> Jeremy Boone (5):
>   tpm: fix potential buffer overruns caused by bit glitches on the bus
>   tpm: st33zp24: fix potential buffer overruns caused by bit glitches on
>     the bus
>   tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches
>     on the bus
>   tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches
>     on the bus
>   tpm_tis: fix potential buffer overruns caused by bit glitches on the
>     bus
> 
>  drivers/char/tpm/st33zp24/st33zp24.c | 4 ++--
>  drivers/char/tpm/tpm-interface.c     | 4 ++++
>  drivers/char/tpm/tpm2-cmd.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 +++--
>  6 files changed, 19 insertions(+), 8 deletions(-)
> 
> -- 
>o 2.12.3

Reviewed-by: Jarkko Sakkinen <jarkko.sakkkinen@linux.intel.com>

I cannot test all of these but I'll put these to linux-next anyway. The
changes are obvious and small scoped so if no one shouts they'll be part
of the next PR.

I've tested the changes that affect tpm2-cmd.c, tpm-interface.c and
tpm_tis_core.c. For HW specific changes tested-by's would be much
appreciated but I don't think they will break anything.

Because these are quite critical fixes I wonder if I could do one more
PR to 4.16?

/Jarkko

  parent reply	other threads:[~2018-02-09 17:13 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 ` [PATCH v2 4/5] tpm_i2c_nuvoton: " James Bottomley
2018-02-08 20:32 ` [PATCH v2 5/5] tpm_tis: " James Bottomley
2018-02-09 17:13 ` Jarkko Sakkinen [this message]
2018-02-09 17:33   ` [PATCH v2 0/2] Fix kernel buffer overruns caused by bit flips 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=20180209171324.ciuw6jadxnoyxty7@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Jeremy.Boone@nccgroup.trust \
    --cc=jmorris@namei.org \
    --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