aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/firmware/efi/libstub/randomalloc.c
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2024-03-15 16:26:16 +0100
committerArd Biesheuvel <ardb@kernel.org>2024-03-15 19:47:09 +0100
commitb3810c5a2cc4a6665f7a65bed5393c75ce3f3aa2 (patch)
treecbd3dc237bd784d9d4cc0c9a5a9d743532470a0c /drivers/firmware/efi/libstub/randomalloc.c
parent021bc4b9d7ed8dcc90dc288e59f120fa6e3087dc (diff)
downloadlinux-b3810c5a2cc4a6665f7a65bed5393c75ce3f3aa2.tar.gz
x86/efistub: Clear decompressor BSS in native EFI entrypoint
The EFI stub on x86 no longer invokes the decompressor as a subsequent boot stage, but calls into the decompression code directly while running in the context of the EFI boot services. This means that when using the native EFI entrypoint (as opposed to the EFI handover protocol, which clears BSS explicitly), the firmware PE image loader is being relied upon to ensure that BSS is zeroed before the EFI stub is entered from the firmware. As Radek's report proves, this is a bad idea. Not all loaders do this correctly, which means some global variables that should be statically initialized to 0x0 may have junk in them. So clear BSS explicitly when entering via efi_pe_entry(). Note that zeroing BSS from C code is not generally safe, but in this case, the following assignment and dereference of a global pointer variable ensures that the memset() cannot be deferred or reordered. Cc: <stable@kernel.org> # v6.1+ Reported-by: Radek Podgorny <radek@podgorny.cz> Closes: https://lore.kernel.org/all/a99a831a-8ad5-4cb0-bff9-be637311f771@podgorny.cz Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/firmware/efi/libstub/randomalloc.c')
0 files changed, 0 insertions, 0 deletions