public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Thomas Huth" <thuth@redhat.com>, linux-efi@vger.kernel.org
Cc: "Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi/capsule-loader: fix incorrect sizeof in phys array reallocation
Date: Fri, 10 Apr 2026 18:11:21 +0200	[thread overview]
Message-ID: <f7c9cc16-4b68-409b-818e-e5c107a5e27b@app.fastmail.com> (raw)
In-Reply-To: <20260410154637.42301-1-thuth@redhat.com>


On Fri, 10 Apr 2026, at 17:46, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> The krealloc() call for cap_info->phys in __efi_capsule_setup_info() uses
> sizeof(phys_addr_t *) instead of sizeof(phys_addr_t), which might be
> causing an undersized allocation.
>
> The allocation is also inconsistent with the initial array allocation in
> efi_capsule_open() that allocates one entry with sizeof(phys_addr_t),
> and the efi_capsule_write() function that stores phys_addr_t values (not
> pointers) via page_to_phys().
>
> On 64-bit systems where sizeof(phys_addr_t) == sizeof(phys_addr_t *), this
> goes unnoticed. On 32-bit systems with PAE where phys_addr_t is 64-bit but
> pointers are 32-bit, this allocates half the required space, which might
> lead to a heap buffer overflow when storing physical addresses.
>
> This is similar to the bug fixed in commit fccfa646ef36 ("efi/capsule-loader:
> fix incorrect allocation size") which fixed the same issue at the initial
> allocation site.
>
> Fixes: f24c4d478013 ("efi/capsule-loader: Reinstate virtual capsule mapping")
> Assisted-by: Claude:claude-sonnet-4-5
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  drivers/firmware/efi/capsule-loader.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Thanks for the fix - I'll queue this up for the next cycle.

> diff --git a/drivers/firmware/efi/capsule-loader.c 
> b/drivers/firmware/efi/capsule-loader.c
> index 2c628a1270919..8e8f81f0a5a0a 100644
> --- a/drivers/firmware/efi/capsule-loader.c
> +++ b/drivers/firmware/efi/capsule-loader.c
> @@ -67,7 +67,7 @@ int __efi_capsule_setup_info(struct capsule_info 
> *cap_info)
>  	cap_info->pages = temp_page;
> 
>  	temp_page = krealloc(cap_info->phys,
> -			     pages_needed * sizeof(phys_addr_t *),
> +			     pages_needed * sizeof(phys_addr_t),
>  			     GFP_KERNEL | __GFP_ZERO);
>  	if (!temp_page)
>  		return -ENOMEM;
> -- 
> 2.53.0

      reply	other threads:[~2026-04-10 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 15:46 [PATCH] efi/capsule-loader: fix incorrect sizeof in phys array reallocation Thomas Huth
2026-04-10 16:11 ` Ard Biesheuvel [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=f7c9cc16-4b68-409b-818e-e5c107a5e27b@app.fastmail.com \
    --to=ardb@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thuth@redhat.com \
    /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