From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Gerald Elder-Vass" <gerald.elder-vass@cloud.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Daniel P . Smith" <dpsmith@apertussolutions.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: [PATCH for-4.21 v2] efi: Protect against unnecessary image unloading
Date: Tue, 14 Oct 2025 14:06:48 +0100 [thread overview]
Message-ID: <20251014130648.2540082-1-andrew.cooper3@citrix.com> (raw)
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>
---
CC: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
CC: Daniel P. Smith <dpsmith@apertussolutions.com>
CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Gerald is OoO and time is tight on Xen 4.21, so I've picked the patch up.
Oleksii: This addresses follow-on feedback for a new feature in Xen 4.21, so
really does want fixing before the release. I forgot to put it on the
tracking list, sorry.
v2:
* Apply feedback as Marek wants it.
---
xen/common/efi/boot.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/xen/common/efi/boot.c b/xen/common/efi/boot.c
index 5b84dbf26e5e..3a78e7571a5e 100644
--- a/xen/common/efi/boot.c
+++ b/xen/common/efi/boot.c
@@ -1062,7 +1062,7 @@ static void __init efi_verify_kernel(EFI_HANDLE ImageHandle)
static EFI_GUID __initdata shim_image_guid = SHIM_IMAGE_LOADER_GUID;
static EFI_GUID __initdata shim_lock_guid = SHIM_LOCK_PROTOCOL_GUID;
SHIM_IMAGE_LOADER *shim_loader;
- EFI_HANDLE loaded_kernel;
+ EFI_HANDLE loaded_kernel = NULL;
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) )
+ shim_loader->UnloadImage(loaded_kernel);
}
/* Otherwise, fall back to SHIM_LOCK. */
base-commit: 53859596c0d34dbca776ec1e47bac8dd90552530
--
2.39.5
next reply other threads:[~2025-10-14 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 13:06 Andrew Cooper [this message]
2025-10-14 13:29 ` [PATCH for-4.21 v2] efi: Protect against unnecessary image unloading Marek Marczykowski-Górecki
2025-10-14 15:57 ` Andrew Cooper
2025-10-14 16:47 ` Marek Marczykowski-Górecki
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=20251014130648.2540082-1-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=gerald.elder-vass@cloud.com \
--cc=marmarek@invisiblethingslab.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).