From: "Gary Lin" <glin@suse.com>
To: devel@edk2.groups.io, ard.biesheuvel@linaro.org
Cc: jian.j.wang@intel.com, hao.a.wu@intel.com, ray.ni@intel.com
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/UefiBootManagerLib: fix crash on uninitialized ExitData
Date: Wed, 17 Apr 2019 10:10:05 +0800 [thread overview]
Message-ID: <20190417021005.GI21677@GaryWorkstation> (raw)
In-Reply-To: <20190416202935.32297-1-ard.biesheuvel@linaro.org>
On Tue, Apr 16, 2019 at 01:29:35PM -0700, Ard Biesheuvel wrote:
> As reported by Gary, the recent LoadImage/StartImage changes to
> accommodate dispatching PE/COFF images built for foreign architectures
> may result in a crash when loading an IA32 option ROM into a X64 VM
> running OVMF:
>
> Loading driver at 0x0007E537000 EntryPoint=0x0007E53C06D 8086100e.efi
> InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7F003B98
> ProtectUefiImageCommon - 0x7F002BC0
> - 0x000000007E537000 - 0x000000000009F900
> Image type IA32 can't be started on X64 UEFI system.
> ASSERT MdeModulePkg/Core/Dxe/Mem/Pool.c(698): Head->Signature == ((('p') |
> ('h' << 8)) | ((('d') | ('0' << 8)) << 16)) || Head->Signature
> == ((('p') | ('h' << 8)) | ((('d') | ('1' << 8)) << 16))
>
> This turns out to be caused by the deferred image loading code in BDS,
> which doesn't check the result code of gBS->StartImage(), and ends up
> trying to free an uninitialized pointer. So ensure ExitData is initialized
> before the call.
>
The fix works for me.
Tested-by: Gary Lin <glin@suse.com>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> MdeModulePkg/Library/UefiBootManagerLib/BmMisc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MdeModulePkg/Library/UefiBootManagerLib/BmMisc.c b/MdeModulePkg/Library/UefiBootManagerLib/BmMisc.c
> index fc8775dfa419..cf99de5b924a 100644
> --- a/MdeModulePkg/Library/UefiBootManagerLib/BmMisc.c
> +++ b/MdeModulePkg/Library/UefiBootManagerLib/BmMisc.c
> @@ -502,6 +502,7 @@ EfiBootManagerDispatchDeferredImages (
> // a 5 Minute period
> //
> gBS->SetWatchdogTimer (5 * 60, 0x0000, 0x00, NULL);
> + ExitData = NULL;
> Status = gBS->StartImage (ImageHandle, &ExitDataSize, &ExitData);
> if (ExitData != NULL) {
> FreePool (ExitData);
> --
> 2.17.1
>
>
>
>
>
next prev parent reply other threads:[~2019-04-17 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 20:29 [PATCH] MdeModulePkg/UefiBootManagerLib: fix crash on uninitialized ExitData Ard Biesheuvel
2019-04-17 2:10 ` Gary Lin [this message]
2019-04-17 6:07 ` Wu, Hao A
2019-04-17 6:23 ` Ard Biesheuvel
2019-04-17 6:30 ` [edk2-devel] " Ni, Ray
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-list 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=20190417021005.GI21677@GaryWorkstation \
--to=devel@edk2.groups.io \
/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