From: Usama Arif <usamaarif642@gmail.com>
To: Gregory Price <gourry@gourry.net>
Cc: ardb@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, leitao@debian.org
Subject: Re: [PATCH] efi: reserve memory for tpm_log only if TPM final events table is valid
Date: Fri, 30 Aug 2024 22:52:48 +0100 [thread overview]
Message-ID: <1a31390d-f452-4d53-84a9-b9fb2af71e4c@gmail.com> (raw)
In-Reply-To: <30f285bc-7540-4d70-8b6c-11675b68e9e4@gmail.com>
On 30/08/2024 17:49, Usama Arif wrote:
>
>
> On 30/08/2024 17:42, Gregory Price wrote:
>> On Fri, Aug 30, 2024 at 10:28:52PM +0100, Usama Arif wrote:
>>> If efi.tpm_log is corrupted, log_tbl->size can be garbage (and
>>> negative). This can result in a large memblock reservation, resulting
>>> in the kernel booting without sufficient memory. Move the memblock
>>> reservation after log_tbl->version check, and check the value of
>>> both tbl_size and memblock_reserve.
>>>
>>> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
>>> ---
>>> drivers/firmware/efi/tpm.c | 16 +++++++++++++---
>>> 1 file changed, 13 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/firmware/efi/tpm.c b/drivers/firmware/efi/tpm.c
>>> index e8d69bd548f3..cfc6a065f441 100644
>>> --- a/drivers/firmware/efi/tpm.c
>>> +++ b/drivers/firmware/efi/tpm.c
>>> @@ -59,9 +59,6 @@ int __init efi_tpm_eventlog_init(void)
>>> return -ENOMEM;
>>> }
>>>
>>> - tbl_size = sizeof(*log_tbl) + log_tbl->size;
>>> - memblock_reserve(efi.tpm_log, tbl_size);
>>> -
>>> if (efi.tpm_final_log == EFI_INVALID_TABLE_ADDR) {
>>> pr_info("TPM Final Events table not present\n");
>>> goto out;
>>
>> The final event table is not present in TCG 1_2 format, but the
>> tpm log still needs to be mapped. So this change is incorrect for
>> v1_2.
>
> hmm so we have
>
> if (efi.tpm_final_log == EFI_INVALID_TABLE_ADDR) {
> pr_info("TPM Final Events table not present\n");
> goto out;
> } else if (log_tbl->version != EFI_TCG2_EVENT_LOG_FORMAT_TCG_2) {
> pr_warn(FW_BUG "TPM Final Events table invalid\n");
> goto out;
> }
>
> If the format is TCG 1_2, then log_tbl is not used?
>
Ah its the case that log_tbl->size will be valid, even if its TCG 2.
Got it, Thanks!
>
>>
>>> @@ -70,6 +67,19 @@ int __init efi_tpm_eventlog_init(void)
>>> goto out;
>>> }
>>>
>>> + tbl_size = sizeof(*log_tbl) + log_tbl->size;
>>> + if (tbl_size < 0) {
>>> + pr_err(FW_BUG "Failed to parse event in TPM Final Events Log\n");
>>> + ret = -EINVAL;
>>> + goto out;
>>> + }
>>> + if (memblock_reserve(efi.tpm_log, tbl_size)) {
>>> + pr_err("TPM Event Log memblock reserve fails 0x%lx - %x\n",
>>> + efi.tpm_log, tbl_size);
>>> + ret = -ENOMEM;
>>> + goto out;
>>> + }
>>> +
>>> final_tbl = early_memremap(efi.tpm_final_log, sizeof(*final_tbl));
>>>
>>> if (!final_tbl) {
>>> --
>>> 2.43.5
>>>
>
next prev parent reply other threads:[~2024-08-30 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 21:28 [PATCH] efi: reserve memory for tpm_log only if TPM final events table is valid Usama Arif
2024-08-30 21:42 ` Gregory Price
2024-08-30 21:49 ` Usama Arif
2024-08-30 21:52 ` Usama Arif [this message]
2024-08-30 21:58 ` Gregory Price
2024-08-30 22:24 ` Usama Arif
2024-08-30 21:54 ` Gregory Price
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=1a31390d-f452-4d53-84a9-b9fb2af71e4c@gmail.com \
--to=usamaarif642@gmail.com \
--cc=ardb@kernel.org \
--cc=gourry@gourry.net \
--cc=leitao@debian.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@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