mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
	"Parthiban" <parthiban@linumiz.com>,
	<James.Bottomley@HansenPartnership.com>
Cc: <linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<peterhuewe@gmx.de>, <jgg@ziepe.ca>
Subject: Re: SLB9670 TPM module crash
Date: Sat, 18 May 2024 14:27:54 +0300	[thread overview]
Message-ID: <D1CQGK8GY5UO.179S3ITUXL00Z@kernel.org> (raw)
In-Reply-To: <D1CQEN4ROQFK.1NHMZGCIL1YC5@kernel.org>

On Sat May 18, 2024 at 2:25 PM EEST, Jarkko Sakkinen wrote:
> On Sat May 18, 2024 at 2:21 PM EEST, Parthiban wrote:
> > Dear James Bottomley,
> >
> > The following crash is observed in the current mainline kernel and I have tried the
> > git bisect to narrow it down. Bisect points to the below commit, which got merged as
> > part of [1]. I tried reverting the below commit and the TPM loads fine.
> >
> > commit 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497
> > Author: James Bottomley <James.Bottomley@HansenPartnership.com>
> > Date:   Mon Apr 29 16:28:07 2024 -0400
> >
> >     tpm: add session encryption protection to tpm2_get_random()
> >     
> >     If some entity is snooping the TPM bus, they can see the random
> >     numbers we're extracting from the TPM and do prediction attacks
> >     against their consumers.  Foil this attack by using response
> >     encryption to prevent the attacker from seeing the random sequence.
> >     
> >     Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> >     Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> >     Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
> >     Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> >
> >  drivers/char/tpm/tpm2-cmd.c | 21 +++++++++++++++++----
> >  1 file changed, 17 insertions(+), 4 deletions(-)
> >
> > [   11.551988] tpm_tis_spi spi0.1: 2.0 TPM (device-id 0x1B, rev-id 22)
> > [   11.563036] spi_master spi0: will run message pump with realtime priority
>
>
> Explanation and workaround: https://lore.kernel.org/linux-integrity/D1C1KL7Q27P9.39BH0Z4EMBBUG@kernel.org/

Oops completely wrong for this issue! Sorry I overlooked.

So fix is in progress for __request_module() issue. See this
discussion for reference:

https://lore.kernel.org/linux-integrity/119dc5ed-f159-41be-9dda-1a056f29888d@notapiano/

BR, Jarkko

      reply	other threads:[~2024-05-18 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 11:21 Parthiban
2024-05-18 11:25 ` Jarkko Sakkinen
2024-05-18 11:27   ` Jarkko Sakkinen [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=D1CQGK8GY5UO.179S3ITUXL00Z@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parthiban@linumiz.com \
    --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®