From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Gerald Elder-Vass <gerald.elder-vass@cloud.com>,
"Daniel P . Smith" <dpsmith@apertussolutions.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH for-4.21 v2] efi: Protect against unnecessary image unloading
Date: Tue, 14 Oct 2025 18:47:53 +0200 [thread overview]
Message-ID: <aO5-ubXGM-u9efiT@mail-itl> (raw)
In-Reply-To: <7a206259-3eb7-4b0c-8437-78579931e56b@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On Tue, Oct 14, 2025 at 04:57:15PM +0100, Andrew Cooper wrote:
> On 14/10/2025 2:29 pm, Marek Marczykowski-Górecki wrote:
> > On Tue, Oct 14, 2025 at 02:06:48PM +0100, Andrew Cooper wrote:
> >> From: Gerald Elder-Vass <gerald.elder-vass@cloud.com>
> >>
> >> Commit 59a1d6d3ea1e introduced Shim's LoadImage protocol and unloads the
> >> image after loading it (for verification purposes) regardless of the
> >> returned status. The protocol API implies this is the correct behaviour
> >> but we should add a check to protect against the unlikely case this
> >> frees any memory in use.
> >>
> >> Signed-off-by: Gerald Elder-Vass <gerald.elder-vass@cloud.com>
> >> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > Reviewed-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
>
> Thanks.
>
> > with one comment below (I'm okay with the patch either way)
> >
> >> EFI_SHIM_LOCK_PROTOCOL *shim_lock;
> >> EFI_STATUS status;
> >> bool verified = false;
> >> @@ -1078,11 +1078,12 @@ static void __init efi_verify_kernel(EFI_HANDLE ImageHandle)
> >> verified = true;
> >>
> >> /*
> >> - * Always unload the image. We only needed LoadImage() to perform
> >> - * verification anyway, and in the case of a failure there may still
> >> - * be cleanup needing to be performed.
> >> + * If the kernel was loaded, unload it. We only needed LoadImage() to
> >> + * perform verification anyway, and in the case of a failure there may
> >> + * still be cleanup needing to be performed.
> >> */
> >> - shim_loader->UnloadImage(loaded_kernel);
> >> + if ( !EFI_ERROR(status) || (status == EFI_SECURITY_VIOLATION) )
> > So, just in case of double-buggy firmware, check loaded_kernel here too?
>
> So to be clear, you're asking for:
>
> loaded_kernel && (!EFI_ERROR(status) || (status == EFI_SECURITY_VIOLATION))
>
> here?
Yes.
> Yeah, can fix that up on commit.
>
> ~Andrew
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-10-14 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 13:06 [PATCH for-4.21 v2] efi: Protect against unnecessary image unloading Andrew Cooper
2025-10-14 13:29 ` Marek Marczykowski-Górecki
2025-10-14 15:57 ` Andrew Cooper
2025-10-14 16:47 ` Marek Marczykowski-Górecki [this message]
2025-10-14 13:38 ` Oleksii Kurochko
2025-10-15 15:04 ` Yann Sionneau
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=aO5-ubXGM-u9efiT@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=gerald.elder-vass@cloud.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).