From: Jarkko Sakkinen <jarkko@kernel.org>
To: Guo Zihao <guozh23@xiaopeng.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Ard Biesheuvel <ardb@kernel.org>,
Matthew Garrett <matthewgarrett@google.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] tpm: efi: reject a final events table with an oversized preboot log
Date: Fri, 6 Nov 2026 17:24:35 +0200 [thread overview]
Message-ID: <au3xM-7onNTtgceh@kernel.org> (raw)
In-Reply-To: <20261106014956.4129904-1-guozh23@xiaopeng.com>
On Fri, Nov 06, 2026 at 09:49:56AM +0800, Guo Zihao wrote:
> The preboot portion recorded in the main event log is subtracted from
> the size of the final events table taken from the firmware:
>
> /*
> * The 'final events log' size excludes the 'final events preboot log'
> * at its beginning.
> */
> final_events_log_size -= log_tbl->final_events_preboot_size;
>
> Both sizes come from EFI configuration tables and are not validated
> against each other. A final events table claiming a preboot portion
> larger than the table itself makes final_events_log_size go negative:
> the subsequent devm_krealloc() can then end up with a wrapped, too
> small allocation, and the memcpy() that appends the final events log
> uses the negative value as its length, running far past the buffer.
>
> The boot path has no way to fix up such a table, so fail the final
> events log instead of appending from it.
>
> Fixes: 166a2809d65b ("tpm: Don't duplicate events from the final event log in the TCG2 log")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guo Zihao <guozh23@xiaopeng.com>
Ditto.
For all four address validation vs bug fix intersection. I did not
check throughly enough to be exactly sure of all four.
Br, Jarkko
next prev parent reply other threads:[~2026-11-06 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 1:49 [PATCH] tpm: efi: reject a final events table with an oversized preboot log Guo Zihao
2026-11-06 9:12 ` Ard Biesheuvel
2026-11-06 9:20 ` [PATCH v2] " Guo Zihao
2026-11-06 15:24 ` Jarkko Sakkinen [this message]
2026-11-09 1:49 ` [PATCH] " Guo Zihao
2026-11-09 14:43 ` Jarkko Sakkinen
2026-11-09 14:45 ` Jarkko Sakkinen
[not found] <au3xN-7onNTtgceh@kernel.org>
2026-11-10 3:08 ` Guo Zihao
2026-11-10 3:58 ` 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=au3xM-7onNTtgceh@kernel.org \
--to=jarkko@kernel.org \
--cc=ardb@kernel.org \
--cc=guozh23@xiaopeng.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=peterhuewe@gmx.de \
--cc=stable@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.