From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Jiangshan Yi <yijiangshan@kylinos.cn>,
Sashiko <sashiko-bot@kernel.org>, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan McDowell <noodles@meta.com>,
Justinien Bouron <jbouron@amazon.com>,
Gunnar Kudrjavets <gunnarku@amazon.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.12.y] tpm: fix off-by-four bounds check in tpm2_get_random()
Date: Mon, 5 Oct 2026 22:19:56 +0300 [thread overview]
Message-ID: <asP4XGM3P1Fdj5Ko@kernel.org> (raw)
In-Reply-To: <2026-10-05-1-daily-reply-0006-tpm-get-random-6.12@kernel.org>
On Mon, Oct 05, 2026 at 09:50:27AM -0400, Sasha Levin wrote:
> > Fix this by checking the response length against 'offset', which
> > already includes the skipped parameter size field.
>
> Queued for 6.12, thanks.
>
> --
> Thanks,
> Sasha
Phew, good to hear, thank you!
There might be for some time more than usual merge conflicts in TPM
driver given making tpm_buf memory layout flat for the sake of being
able to use __free for of its allocations, and thus completely
prevent any possible memory leaks from transient buffers.
Right, and also merge conflicts could happen also in trusted keys.
They are cheap to fix and I'll monitor this situation proactively,
and try to react fast.
Br, Jarkko
prev parent reply other threads:[~2026-10-05 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026100308-drew-squeamish-a28c@gregkh>
2026-10-05 7:59 ` Jarkko Sakkinen
2026-10-05 13:50 ` Sasha Levin
2026-10-05 19:19 ` 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=asP4XGM3P1Fdj5Ko@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=gunnarku@amazon.com \
--cc=jbouron@amazon.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noodles@meta.com \
--cc=peterhuewe@gmx.de \
--cc=sashal@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yijiangshan@kylinos.cn \
/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®