From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Kees Cook <kees@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] efi: Replace efi_memory_attributes_table_t 0-sized array with flexible array
Date: Wed, 10 Jul 2024 17:32:13 -0600 [thread overview]
Message-ID: <d2b9e11a-749b-47cd-9cc2-0734ec5849b0@embeddedor.com> (raw)
In-Reply-To: <20240710225538.work.224-kees@kernel.org>
On 10/07/24 16:55, Kees Cook wrote:
> While efi_memory_attributes_table_t::entry isn't used directly as an
> array, it is used as a base for pointer arithmetic. The type is wrong
> as it's not technically an array of efi_memory_desc_t's; they could be
> larger. Regardless, leave the type unchanged and remove the old style
> "0" array size. Additionally replace the open-coded entry offset code
> with the existing efi_early_memdesc_ptr() helper.
>
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: linux-efi@vger.kernel.org
> ---
> drivers/firmware/efi/memattr.c | 2 +-
> include/linux/efi.h | 6 +++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/efi/memattr.c b/drivers/firmware/efi/memattr.c
> index ab85bf8e165a..01142604e8df 100644
> --- a/drivers/firmware/efi/memattr.c
> +++ b/drivers/firmware/efi/memattr.c
> @@ -164,7 +164,7 @@ int __init efi_memattr_apply_permissions(struct mm_struct *mm,
> bool valid;
> char buf[64];
>
> - valid = entry_is_valid((void *)tbl->entry + i * tbl->desc_size,
> + valid = entry_is_valid(efi_early_memdesc_ptr(tbl->entry, tbl->desc_size, i),
> &md);
> size = md.num_pages << EFI_PAGE_SHIFT;
> if (efi_enabled(EFI_DBG) || !valid)
> diff --git a/include/linux/efi.h b/include/linux/efi.h
> index 418e555459da..b06639c4f6a5 100644
> --- a/include/linux/efi.h
> +++ b/include/linux/efi.h
> @@ -607,7 +607,11 @@ typedef struct {
> u32 num_entries;
> u32 desc_size;
> u32 flags;
> - efi_memory_desc_t entry[0];
> + /*
> + * There are @num_entries following, each of size @desc_size bytes,
> + * including an efi_memory_desc_t header.
> + */
> + efi_memory_desc_t entry[];
a candidate for future __counted_by(num_entries * desc_size) ? :p
Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Thanks
--
Gustavo
> } efi_memory_attributes_table_t;
>
> typedef struct {
next prev parent reply other threads:[~2024-07-10 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 22:55 [PATCH] efi: Replace efi_memory_attributes_table_t 0-sized array with flexible array Kees Cook
2024-07-10 23:32 ` Gustavo A. R. Silva [this message]
2024-07-10 23:34 ` Gustavo A. R. Silva
2024-07-11 6:05 ` Ard Biesheuvel
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=d2b9e11a-749b-47cd-9cc2-0734ec5849b0@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=ardb@kernel.org \
--cc=kees@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-hardening@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