efi: x86: Use strict W^X mappings in PE/COFF header
Ard Biesheuvel
maintainercover efi: x86: Use strict W^X mappings in PE/COFF header
This is a follow-up to work proposed by Evgeny to tighten memory permissions used by the EFI stub and subsequently by the decompressor on x86.
Instead of going out of our way to make more space in the first 500 bytes of the image, and relying on non-1:1 mapped sections (which is risky in the context of bespoke PE loaders), these patches reorganize the header so the PE header comes after the x86 setup header, and can be extended at will.
I pushed a branch at [1] that combines this with v4 of Evgeny's series (after some minor surgery, e.g., to reorder the text and rodata sections so they are contiguous)
We might split off the rodata section as well, and give it read/non-exec permissions, but I'd like to discuss the approach first, and perhaps get some testing data points.
[0] https://lore.kernel.org/linux-efi/[email protected]/
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-x86-nx-v4
Ard Biesheuvel (4):
efi: x86: Use private copy of struct setup_header
efi: x86: Move PE header after setup header
efi: x86: Drop alignment section header flags
efi: x86: Split PE/COFF .text section into .text and .data
arch/x86/boot/Makefile | 2 +- arch/x86/boot/header.S | 52 +++++++++----------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 38 +++++++++----- drivers/firmware/efi/libstub/x86-stub.c | 43 +++------------- 5 files changed, 59 insertions(+), 77 deletions(-)
Signature · 1 line
2.39.2
Ard Biesheuvel
maintainerRFC PATCH 1/4 efi: x86: Use private copy of struct setup_header
The native EFI entrypoint does not take a struct boot_params from the loader, but instead, it constructs one from scratch, using the setup header data from the start of the image.
This setup header is placed in a way that permits legacy loaders to manipulate the contents (i.e., to pass the kernel command line or the address and size of an initial ramdisk), but EFI boot does not use it in that way - it only copies the contents that were placed there at build time, but EFI loaders will not (and should not) manipulate the setup header to configure the boot. (Commit 63bf28ceb3ebbe76 "efi: x86: Wipe setup_data on pure EFI boot" deals with some of the fallout of using setup_data in a way that breaks EFI boot.) So having a pristine, private copy of the setup header rather than copying the one legacy boot loaders use would be an advantage for EFI boot.
As it turns out, there is another reason why copying this header is slightly problematic: the fixed offset of 0x1f1 bytes into the image makes it difficult to describe all the sections of the image, as we are running out of space. We could mitigate this by placing some parts of the PE/COFF header after this setup header (which will happen in a subsequent patch), but this makes the setup_header fundamentally part of the PE header as well, which means that it is no longer part of the 'in-memory' representation of the PE image, but only part of the 'on-disk' representation. This means copying the setup header from the running image may not work, as the PE loader may not have put it in memory to begin with.
So let's work around this, and simplify things at the same time, by just copying the setup header into a EFI stub private allocation at build time, and use that instead of copying it from the loaded image after it has been started.
--- arch/x86/boot/Makefile | 2 +- arch/x86/boot/tools/build.c | 8 ++++ drivers/firmware/efi/libstub/x86-stub.c | 43 +++----------------- 3 files changed, 15 insertions(+), 38 deletions(-)
arch/x86/boot/Makefile +1 -1
@@ -91,7 +91,7 @@ $(obj)/vmlinux.bin: $(obj)/compressed/vmlinux FORCE SETUP_OBJS = $(addprefix $(obj)/,$(setup-y)) -sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z] \(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|input_data\|kernel_info\|_end\|_ehead\|_text\|z_.*\)$$/\#define ZO_\2 0x\1/p' +sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z] \(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|efi_boot_params\|input_data\|kernel_info\|_end\|_ehead\|_text\|z_.*\)$$/\#define ZO_\2 0x\1/p' quiet_cmd_zoffset = ZOFFSET $@ cmd_zoffset = $(NM) $< | sed -n $(sed-zoffset) > $@
arch/x86/boot/tools/build.c +8 -0
@@ -115,6 +115,7 @@ static unsigned long efi32_stub_entry;static unsigned long efi64_stub_entry;static unsigned long efi_pe_entry;static unsigned long efi32_pe_entry; +static unsigned long efi_boot_params;static unsigned long kernel_info;static unsigned long startup_64;static unsigned long _ehead;
@@ -453,6 +454,7 @@ static void parse_zoffset(char *fname)PARSE_ZOFS (p, efi64_stub_entry);PARSE_ZOFS (p, efi_pe_entry);PARSE_ZOFS (p, efi32_pe_entry); +PARSE_ZOFS (p, efi_boot_params);PARSE_ZOFS (p, kernel_info);PARSE_ZOFS (p, startup_64);PARSE_ZOFS (p, _ehead);
@@ -589,6 +591,12 @@ int main(int argc, char **argv)memcpy (output + setup_size, kernel, kern_file_size);memset (output + setup_size + kern_file_size,0 , kern_size - kern_file_size); +#ifdef CONFIG_EFI_STUB +/* Copy the setup header */ +memcpy (output + setup_size + efi_boot_params +0x1f1 , &buf[0x1f1 ], +0x290 -0x1f1 /* == max possible sizeof(struct setup_header) */ ); +#endif +/* Calculate and write kernel checksum. */ crc =partial_crc32 (output, total_size -4 , crc);put_unaligned_le32 (crc, &output[total_size -4 ]);
drivers/firmware/efi/libstub/x86-stub.c +6 -37
74 lines not on this page · raw message
Signature · 1 line
2.39.2
Ard Biesheuvel
maintainerRFC PATCH 3/4 efi: x86: Drop alignment section header flags
In reply to Ard BiesheuvelThe section header flags for alignment are documented as only being applicable to PE object files, not PE executables, so let's drop them.
--- arch/x86/boot/header.S | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-)
arch/x86/boot/header.S +3 -6
@@ -212,8 +212,7 @@ section_table: .word 0 # NumberOfLineNumbers .long IMAGE_SCN_CNT_INITIALIZED_DATA | \ IMAGE_SCN_MEM_READ | \ - IMAGE_SCN_MEM_DISCARDABLE | \ - IMAGE_SCN_ALIGN_1BYTES # Characteristics + IMAGE_SCN_MEM_DISCARDABLE # Characteristics #ifdef CONFIG_EFI_MIXED #
@@ -231,8 +230,7 @@ section_table: .word 0 # NumberOfLineNumbers .long IMAGE_SCN_CNT_INITIALIZED_DATA | \ IMAGE_SCN_MEM_READ | \ - IMAGE_SCN_MEM_DISCARDABLE | \ - IMAGE_SCN_ALIGN_1BYTES # Characteristics + IMAGE_SCN_MEM_DISCARDABLE # Characteristics #endif #
@@ -253,8 +251,7 @@ section_table: .word 0 # NumberOfLineNumbers .long IMAGE_SCN_CNT_CODE | \ IMAGE_SCN_MEM_READ | \ - IMAGE_SCN_MEM_EXECUTE | \ - IMAGE_SCN_ALIGN_16BYTES # Characteristics + IMAGE_SCN_MEM_EXECUTE # Characteristics .set section_count, (. - section_table) / 40 #endif /* CONFIG_EFI_STUB */
Signature · 1 line
2.39.2
Ard Biesheuvel
maintainerRFC PATCH 2/4 efi: x86: Move PE header after setup header
In reply to Ard BiesheuvelWe are currently limited in the number of PE/COFF sections we can describe in the PE header, due to lack of space. This is caused by the presence of the setup header at offset 0x1f1, leaving only the space before it for PE metadata.
However, now that we no longer copy the setup_header from this part of the image for use by the EFI stub, we no longer have to describe it as part of the loadable image. This means we can put the PE header *after* the setup header, and use as much space as we like. It also means we don't have to describe this part of the image in PE/COFF, and simply treat it as part of the header. This means we can drop the ".setup" section as well.
--- arch/x86/boot/header.S | 26 +++----------------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 11 +++------ 3 files changed, 9 insertions(+), 29 deletions(-)
arch/x86/boot/header.S +4 -22
@@ -85,7 +85,7 @@ bs_die: # Offset to the PE header. # .long LINUX_PE_MAGIC - .long pe_header + .long pe_header - bootsect_start #endif /* CONFIG_EFI_STUB */ .section ".bsdata", "a"
@@ -96,6 +96,8 @@ bugger_off_msg: .byte 0 #ifdef CONFIG_EFI_STUB + .section ".peheader", "a" + .align 8 pe_header: .long PE_MAGIC
@@ -161,7 +163,7 @@ extra_header_fields: # .long 0 # SizeOfImage - .long 0x200 # SizeOfHeaders + .long 0x800 # SizeOfHeaders .long 0 # CheckSum .word IMAGE_SUBSYSTEM_EFI_APPLICATION # Subsystem (EFI application) #ifdef CONFIG_EFI_DXE_MEM_ATTRIBUTES
@@ -192,26 +194,6 @@ extra_header_fields: # Section table section_table: - # - # The offset & size fields are filled in by build.c. - # - .ascii ".setup" - .byte 0 - .byte 0 - .long 0 - .long 0x0 # startup_{32,64} - .long 0 # Size of initialized data - # on disk - .long 0x0 # startup_{32,64} - .long 0 # PointerToRelocations - .long 0 # PointerToLineNumbers - .word 0 # NumberOfRelocations - .word 0 # NumberOfLineNumbers - .long IMAGE_SCN_CNT_CODE | \ - IMAGE_SCN_MEM_READ | \ - IMAGE_SCN_MEM_EXECUTE | \ - IMAGE_SCN_ALIGN_16BYTES # Characteristics - # # The EFI application loader requires a relocation section # because EFI applications must be relocatable. The .reloc
arch/x86/boot/setup.ld +1 -0
@@ -16,6 +16,7 @@ SECTIONS . = 495; .header : { *(.header) } .entrytext : { *(.entrytext) } + .peheader : { *(.peheader) } .inittext : { *(.inittext) } .initdata : { *(.initdata) } __end_init = .;
arch/x86/boot/tools/build.c +4 -7
@@ -296,16 +296,13 @@ static void update_pecoff_section_header(char *section_name, uint32_t offset, uiupdate_pecoff_section_header_fields (section_name, offset, size, size, offset); } -static void update_pecoff_setup_and_reloc (unsigned int size) +static void update_pecoff_reloc (unsigned int size) { -uint32_t setup_offset =SECTOR_SIZE ;uint32_t reloc_offset = size -PECOFF_RELOC_RESERVE -PECOFF_COMPAT_RESERVE ;#ifdef CONFIG_EFI_MIXED uint32_t compat_offset = reloc_offset +PECOFF_RELOC_RESERVE ;#endif -uint32_t setup_size = reloc_offset - setup_offset; -update_pecoff_section_header (".setup" , setup_offset, setup_size);update_pecoff_section_header (".reloc" , reloc_offset,PECOFF_RELOC_RESERVE );/*
@@ -353,7 +350,7 @@ static unsigned int update_pecoff_sections(unsigned int text_start, unsigned int* Size of code: Subtract the size of the first sector (512 bytes) * which includes the header. */ -put_unaligned_le32 (file_sz -SECTOR_SIZE + bss_sz, &hdr->text_size); +put_unaligned_le32 (text_sz + bss_sz, &hdr->text_size);/* Size of image */ put_unaligned_le32 (init_sz, &hdr->image_size);
@@ -407,7 +404,7 @@ static void efi_stub_entry_update(void)#else -static inline void update_pecoff_setup_and_reloc (unsigned int size) {} +static inline void update_pecoff_reloc (unsigned int size) {}static inline void update_pecoff_text (unsigned int text_start,unsigned int file_sz,unsigned int init_sz) {}
@@ -542,7 +539,7 @@ int main(int argc, char **argv)#ifdef CONFIG_EFI_STUB /* PE specification require 512-byte minimum section file alignment */ kern_size =round_up (kern_file_size +4 ,SECTOR_SIZE ); -update_pecoff_setup_and_reloc (setup_size); +update_pecoff_reloc (setup_size);#else /* Number of 16-byte paragraphs, including space for a 4-byte CRC */ kern_size =round_up (kern_file_size +4 ,PARAGRAPH_SIZE );
Signature · 1 line
2.39.2
Ard Biesheuvel
maintainerRFC PATCH 4/4 efi: x86: Split PE/COFF .text section into .text and .data
In reply to Ard BiesheuvelModern PE loader implementations used by EFI will honour the PE section permission attributes, and so we can use them to avoid mappings that are writable and executable at the same time.
--- arch/x86/boot/header.S | 17 ++++++++++++++++ arch/x86/boot/tools/build.c | 21 +++++++++++++++----- 2 files changed, 33 insertions(+), 5 deletions(-)
arch/x86/boot/header.S +17 -0
@@ -253,6 +253,23 @@ section_table: IMAGE_SCN_MEM_READ | \ IMAGE_SCN_MEM_EXECUTE # Characteristics + .ascii ".data" + .byte 0 + .byte 0 + .byte 0 + .long 0 + .long 0x0 # startup_{32,64} + .long 0 # Size of initialized data + # on disk + .long 0x0 # startup_{32,64} + .long 0 # PointerToRelocations + .long 0 # PointerToLineNumbers + .word 0 # NumberOfRelocations + .word 0 # NumberOfLineNumbers + .long IMAGE_SCN_CNT_INITIALIZED_DATA | \ + IMAGE_SCN_MEM_READ | \ + IMAGE_SCN_MEM_WRITE # Characteristics + .set section_count, (. - section_table) / 40 #endif /* CONFIG_EFI_STUB */
arch/x86/boot/tools/build.c +16 -5
@@ -119,6 +119,7 @@ static unsigned long efi_boot_params;static unsigned long kernel_info;static unsigned long startup_64;static unsigned long _ehead; +static unsigned long _data;static unsigned long _end;/*----------------------------------------------------------------------*/
@@ -347,10 +348,15 @@ static unsigned int update_pecoff_sections(unsigned int text_start, unsigned int init_sz +=CONFIG_PHYSICAL_ALIGN ;/* -* Size of code: Subtract the size of the first sector (512 bytes) -* which includes the header. +* Size of code: the size of the combined .text/.rodata section, which +* ends at the _data marker symbol. */ -put_unaligned_le32 (text_sz + bss_sz, &hdr->text_size); +put_unaligned_le32 (_data, &hdr->text_size); + +/* +* Size of data: the size of the combined .data/.bss section. +*/ +put_unaligned_le32 (text_sz - _data + bss_sz, &hdr->data_size);/* Size of image */ put_unaligned_le32 (init_sz, &hdr->image_size);
@@ -360,9 +366,13 @@ static unsigned int update_pecoff_sections(unsigned int text_start, unsigned int*/ put_unaligned_le32 (text_start + efi_pe_entry, &hdr->entry_point); -update_pecoff_section_header_fields (".text" , text_start, text_sz + bss_sz, - text_sz, text_start); +update_pecoff_section_header_fields (".text" , text_start, _data, + _data, text_start); +update_pecoff_section_header_fields (".data" , text_start + _data, + text_sz - _data + bss_sz, + text_sz - _data, + text_start + _data);return text_start + file_sz; }
@@ -455,6 +465,7 @@ static void parse_zoffset(char *fname)PARSE_ZOFS (p, kernel_info);PARSE_ZOFS (p, startup_64);PARSE_ZOFS (p, _ehead); +PARSE_ZOFS (p, _data);PARSE_ZOFS (p, _end); p =strchr (p,'\n' );
Signature · 1 line
2.39.2
Ard Biesheuvel
maintainerRe: [RFC PATCH 2/4] efi: x86: Move PE header after setup header
In reply to Ard BiesheuvelQuoted 6 lines · Ard Biesheuvel
We are currently limited in the number of PE/COFF sections we can describe in the PE header, due to lack of space. This is caused by the presence of the setup header at offset
0x1f1, leaving only the space before it for PE metadata.
Quoted 8 lines
However, now that we no longer copy the
setup_headerfrom this part of the image for use by the EFI stub, we no longer have to describe it as part of the loadable image. This means we can put the PE header *after* the setup header, and use as much space as we like. It also means we don't have to describe this part of the image in PE/COFF, and simply treat it as part of the header. This means we can drop the ".setup" section as well.
Better idea: let's just rip out the ancient real mode boot code. It's 20+ years old and only prints an error message in case the kernel is booted in a way that has not been supported for all that time.
Comments anyone?
Quoted 129 lines
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/x86/boot/header.S | 26 +++----------------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 11 +++------ 3 files changed, 9 insertions(+), 29 deletions(-)arch/x86/boot/header.S +4
-22@@ -85,7 +85,7 @@ bs_die: # Offset to the PE header. # .long LINUX_PE_MAGIC - .long pe_header + .long pe_header - bootsect_start #endif /* CONFIG_EFI_STUB */ .section ".bsdata", "a"@@ -96,6 +96,8 @@ bugger_off_msg: .byte 0 #ifdef CONFIG_EFI_STUB + .section ".peheader", "a" + .align 8 pe_header: .long PE_MAGIC@@ -161,7 +163,7 @@ extra_header_fields: # .long 0 # SizeOfImage - .long 0x200 # SizeOfHeaders + .long 0x800 # SizeOfHeaders .long 0 # CheckSum .word IMAGE_SUBSYSTEM_EFI_APPLICATION # Subsystem (EFI application) #ifdef CONFIG_EFI_DXE_MEM_ATTRIBUTES@@ -192,26 +194,6 @@ extra_header_fields: # Section table section_table: - # - # The offset & size fields are filled in by build.c. - # - .ascii ".setup" - .byte 0 - .byte 0 - .long 0 - .long 0x0 # startup_{32,64} - .long 0 # Size of initialized data - # on disk - .long 0x0 # startup_{32,64} - .long 0 # PointerToRelocations - .long 0 # PointerToLineNumbers - .word 0 # NumberOfRelocations - .word 0 # NumberOfLineNumbers - .long IMAGE_SCN_CNT_CODE | \ - IMAGE_SCN_MEM_READ | \ - IMAGE_SCN_MEM_EXECUTE | \ - IMAGE_SCN_ALIGN_16BYTES # Characteristics - # # The EFI application loader requires a relocation section # because EFI applications must be relocatable. The .relocarch/x86/boot/setup.ld +1
-0@@ -16,6 +16,7 @@ SECTIONS . = 495; .header : { *(.header) } .entrytext : { *(.entrytext) } + .peheader : { *(.peheader) } .inittext : { *(.inittext) } .initdata : { *(.initdata) } __end_init = .;arch/x86/boot/tools/build.c +4
-8@@ -296,16 +296,13 @@ static void update_pecoff_section_header(char *section_name, uint32_t offset, uiupdate_pecoff_section_header_fields (section_name, offset, size, size, offset); } -static void update_pecoff_setup_and_reloc (unsigned int size) +static void update_pecoff_reloc (unsigned int size) { -uint32_t setup_offset =SECTOR_SIZE ;uint32_t reloc_offset = size -PECOFF_RELOC_RESERVE -PECOFF_COMPAT_RESERVE ;#ifdef CONFIG_EFI_MIXED uint32_t compat_offset = reloc_offset +PECOFF_RELOC_RESERVE ;#endif -uint32_t setup_size = reloc_offset - setup_offset; -update_pecoff_section_header (".setup" , setup_offset, setup_size);update_pecoff_section_header (".reloc" , reloc_offset,PECOFF_RELOC_RESERVE );/* @@ -353,7 +350,7 @@ static unsigned int update_pecoff_sections(unsigned int text_start, unsigned int* Size of code: Subtract the size of the first sector (512 bytes) * which includes the header. */ -put_unaligned_le32 (file_sz -SECTOR_SIZE + bss_sz, &hdr->text_size); +put_unaligned_le32 (text_sz + bss_sz, &hdr->text_size);/* Size of image */ put_unaligned_le32 (init_sz, &hdr->image_size);@@ -407,7 +404,7 @@ static void efi_stub_entry_update(void)#else -static inline void update_pecoff_setup_and_reloc (unsigned int size) {} +static inline void update_pecoff_reloc (unsigned int size) {}static inline void update_pecoff_text (unsigned int text_start,unsigned int file_sz,unsigned int init_sz) {}@@ -542,7 +539,7 @@ int main(int argc, char **argv)#ifdef CONFIG_EFI_STUB /* PE specification require 512-byte minimum section file alignment */ kern_size =round_up (kern_file_size +4 ,SECTOR_SIZE ); -update_pecoff_setup_and_reloc (setup_size); +update_pecoff_reloc (setup_size);#else /* Number of 16-byte paragraphs, including space for a 4-byte CRC */ kern_size =round_up (kern_file_size +4 ,PARAGRAPH_SIZE ); --2.39.2
Quoted 33 lines · Ard Biesheuvel
This is a follow-up to work proposed by Evgeny to tighten memory permissions used by the EFI stub and subsequently by the decompressor on x86.
Instead of going out of our way to make more space in the first 500 bytes of the image, and relying on non-1:1 mapped sections (which is risky in the context of bespoke PE loaders), these patches reorganize the header so the PE header comes after the x86 setup header, and can be extended at will.
I pushed a branch at [1] that combines this with v4 of Evgeny's series (after some minor surgery, e.g., to reorder the text and rodata sections so they are contiguous)
We might split off the rodata section as well, and give it read/non-exec permissions, but I'd like to discuss the approach first, and perhaps get some testing data points.
Cc Evgeniy Baskov <[email protected]>Cc Borislav Petkov <[email protected]>Cc Alexey Khoroshilov <[email protected]>Cc Peter Jones <[email protected]>Cc "Limonciello, Mario" <[email protected]>[0] https://lore.kernel.org/linux-efi/[email protected]/
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-x86-nx-v4Ard Biesheuvel (4):
efi: x86: Use private copy of structsetup_header
efi: x86: Move PE header after setup header
efi: x86: Drop alignment section header flags
efi: x86: Split PE/COFF .text section into .text and .data
Quoted 6 lines
arch/x86/boot/Makefile | 2 +- arch/x86/boot/header.S | 52 +++++++++----------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 38 +++++++++----- drivers/firmware/efi/libstub/x86-stub.c | 43 +++------------- 5 files changed, 59 insertions(+), 77 deletions(-)
I've quickly looked through these patches but I'll do more testing tomorrow.
This approach seems to be better than mine if it will work. I've tried the similar thing but I did not think of creating the local copy of the bootparams and the attempt to map them did not work since the PE loader I am trying to get kernel booting with does not accept sections before the PE header. But since the bootparams is inside the padding and is not used, it should be fine.
But this will still need more changes to work properly with stricter PE loaders like the one that I've mentioned in my patch series [1].
The image should also have 4K aligned section virtual addresses and sizes (even on .reloc and .compat AFAIK), otherwise UEFI will ignore memory attributes (or refuse to load the kernel). Another desired thing is having adjacent section with no padding in between them, since [1] does have a mode that requires sections them to be adjacent. (SizeOfHeaders/header_size should also be set to the size of setup since it is also checked to be adjacent to the first section.)
I did not do the one-to-one mapping of file and virtual addresses since it would require almost 4K paddings for the auxiliary sections.
[1] https://github.com/acidanthera/audk/tree/secure_pe
Thanks,
Evgeniy Baskov
Re: [RFC PATCH 4/4] efi: x86: Split PE/COFF .text section into .text and .data
In reply to Ard BiesheuvelQuoted 91 lines · Ard Biesheuvel
Modern PE loader implementations used by EFI will honour the PE section permission attributes, and so we can use them to avoid mappings that are writable and executable at the same time.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/x86/boot/header.S | 17 ++++++++++++++++ arch/x86/boot/tools/build.c | 21 +++++++++++++++----- 2 files changed, 33 insertions(+), 5 deletions(-)arch/x86/boot/header.S +17
-0@@ -253,6 +253,23 @@ section_table: IMAGE_SCN_MEM_READ | \ IMAGE_SCN_MEM_EXECUTE # Characteristics + .ascii ".data" + .byte 0 + .byte 0 + .byte 0 + .long 0 + .long 0x0 # startup_{32,64} + .long 0 # Size of initialized data + # on disk + .long 0x0 # startup_{32,64} + .long 0 # PointerToRelocations + .long 0 # PointerToLineNumbers + .word 0 # NumberOfRelocations + .word 0 # NumberOfLineNumbers + .long IMAGE_SCN_CNT_INITIALIZED_DATA | \ + IMAGE_SCN_MEM_READ | \ + IMAGE_SCN_MEM_WRITE # Characteristics + .set section_count, (. - section_table) / 40 #endif /* CONFIG_EFI_STUB */arch/x86/boot/tools/build.c +1
-0@@ -119,6 +119,7 @@ static unsigned long efi_boot_params;static unsigned long kernel_info;static unsigned long startup_64;static unsigned long _ehead; +static unsigned long _data;static unsigned long _end;/*----------------------------------------------------------------------*/
arch/x86/boot/tools/build.c +0
-0@@ -347,10 +348,15 @@ static unsigned intupdate_pecoff_sections(unsigned int
text_start, unsigned intarch/x86/boot/tools/build.c +1
-2init_sz +=CONFIG_PHYSICAL_ALIGN ;/* -* Size of code: Subtract the size of the first sector (512 bytes) -* which includes the header. +* Size of code: the size of the combined .text/.rodata section, which
arch/x86/boot/tools/build.c +7
-1+* ends at the _data marker symbol. */ -put_unaligned_le32 (text_sz + bss_sz, &hdr->text_size); +put_unaligned_le32 (_data, &hdr->text_size); + +/* +* Size of data: the size of the combined .data/.bss section. +*/ +put_unaligned_le32 (text_sz - _data + bss_sz, &hdr->data_size);/* Size of image */ put_unaligned_le32 (init_sz, &hdr->image_size);@@ -360,9 +366,13 @@ static unsigned intupdate_pecoff_sections(unsigned int
text_start, unsigned intarch/x86/boot/tools/build.c +0
-1*/ put_unaligned_le32 (text_start + efi_pe_entry, &hdr->entry_point); - update_pecoff_section_header_fields(".text", text_start, text_sz +
bss_sz,arch/x86/boot/tools/build.c +6
-1- text_sz, text_start); +update_pecoff_section_header_fields (".text" , text_start, _data, + _data, text_start); +update_pecoff_section_header_fields (".data" , text_start + _data, + text_sz - _data + bss_sz, + text_sz - _data, + text_start + _data);return text_start + file_sz; }
arch/x86/boot/tools/build.c static void parse_zoffset(char *fname) · line 468
Quoted 4 lines
arch/x86/boot/tools/build.c +1
-0@@ -455,6 +465,7 @@ static void parse_zoffset(char *fname)PARSE_ZOFS (p, kernel_info);PARSE_ZOFS (p, startup_64);PARSE_ZOFS (p, _ehead); +PARSE_ZOFS (p, _data);
This also requires _data to be fetched to zoffset.h:
arch/x86/boot/Makefile +1 -1
@@ -91,7 +91,7 @@ $(obj)/vmlinux.bin: $(obj)/compressed/vmlinux FORCE SETUP_OBJS = $(addprefix $(obj)/,$(setup-y)) -sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z] \(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|efi_boot_params\|input_data\|kernel_info\|_end\|_ehead\|_text\|z_.*\)$$/\#define ZO_\2 0x\1/p' +sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z] \(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|efi_boot_params\|input_data\|kernel_info\|_end\|_ehead\|_text\|_data\|z_.*\)$$/\#define ZO_\2 0x\1/p' quiet_cmd_zoffset = ZOFFSET $@ cmd_zoffset = $(NM) $< | sed -n $(sed-zoffset) > $@
Quoted 3 lines
arch/x86/boot/tools/build.c +0
-0PARSE_ZOFS (p, _end); p =strchr (p,'\n' );
Ard Biesheuvel
maintainerRe: [RFC PATCH 4/4] efi: x86: Split PE/COFF .text section into .text and .data
Quoted 93 lines · Evgeniy Baskov
Quoted 91 lines · Ard Biesheuvel
Modern PE loader implementations used by EFI will honour the PE section permission attributes, and so we can use them to avoid mappings that are
writable and executable at the same time.Signed-off-by Ard Biesheuvel <[email protected]>--- arch/x86/boot/header.S | 17 ++++++++++++++++ arch/x86/boot/tools/build.c | 21 +++++++++++++++----- 2 files changed, 33 insertions(+), 5 deletions(-)arch/x86/boot/header.S +17
-0@@ -253,6 +253,23 @@ section_table: IMAGE_SCN_MEM_READ | \ IMAGE_SCN_MEM_EXECUTE # Characteristics + .ascii ".data" + .byte 0 + .byte 0 + .byte 0 + .long 0 + .long 0x0 # startup_{32,64} + .long 0 # Size of initialized data + # on disk + .long 0x0 # startup_{32,64} + .long 0 # PointerToRelocations + .long 0 # PointerToLineNumbers + .word 0 # NumberOfRelocations + .word 0 # NumberOfLineNumbers + .long IMAGE_SCN_CNT_INITIALIZED_DATA | \ + IMAGE_SCN_MEM_READ | \ + IMAGE_SCN_MEM_WRITE # Characteristics + .set section_count, (. - section_table) / 40 #endif /* CONFIG_EFI_STUB */arch/x86/boot/tools/build.c +1
-0@@ -119,6 +119,7 @@ static unsigned long efi_boot_params;static unsigned long kernel_info;static unsigned long startup_64;static unsigned long _ehead; +static unsigned long _data;static unsigned long _end;/*----------------------------------------------------------------------*/
arch/x86/boot/tools/build.c +0
-0@@ -347,10 +348,15 @@ static unsigned intupdate_pecoff_sections(unsigned int
text_start, unsigned intinit_sz += CONFIG_PHYSICAL_ALIGN; /*arch/x86/boot/tools/build.c +1
-2-* Size of code: Subtract the size of the first sector (512 bytes) -* which includes the header. +* Size of code: the size of the combined .text/.rodata section, which
arch/x86/boot/tools/build.c +7
-1+* ends at the _data marker symbol. */ -put_unaligned_le32 (text_sz + bss_sz, &hdr->text_size); +put_unaligned_le32 (_data, &hdr->text_size); + +/* +* Size of data: the size of the combined .data/.bss section. +*/ +put_unaligned_le32 (text_sz - _data + bss_sz, &hdr->data_size);/* Size of image */ put_unaligned_le32 (init_sz, &hdr->image_size);@@ -360,9 +366,13 @@ static unsigned intupdate_pecoff_sections(unsigned int
text_start, unsigned int*/ put_unaligned_le32(text_start + efi_pe_entry, &hdr->entry_point);- update_pecoff_section_header_fields(".text",
text_start,text_sz+bss_sz,arch/x86/boot/tools/build.c +6
-1- text_sz, text_start); +update_pecoff_section_header_fields (".text" , text_start, _data, + _data, text_start); +update_pecoff_section_header_fields (".data" , text_start + _data, + text_sz - _data + bss_sz, + text_sz - _data, + text_start + _data);return text_start + file_sz; }
Quoted 8 lines
arch/x86/boot/tools/build.c static void parse_zoffset(char *fname) · line 468
Quoted 5 lines
arch/x86/boot/tools/build.c +1
-0@@ -455,6 +465,7 @@ static void parse_zoffset(char *fname)PARSE_ZOFS (p, kernel_info);PARSE_ZOFS (p, startup_64);PARSE_ZOFS (p, _ehead); +PARSE_ZOFS (p, _data);This also requires
_datato be fetched tozoffset.h:
Indeed - I'd fixed that locally but failed to include it in the patch, apologies.
Quoted 21 lines
arch/x86/boot/Makefile +0
-1@@ -91,7 +91,7 @@ $(obj)/vmlinux.bin: $(obj)/compressed/vmlinux FORCE SETUP_OBJS = $(addprefix $(obj)/,$(setup-y)) -sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z]\(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|efi_boot_params\|input_data\|kernel_info\|_end\|_ehead\|_text\|z_.*\)$$/\#define ZO_\2 0x\1/p'
+sed-zoffset := -e 's/^\([0-9a-fA-F]*\) [a-zA-Z] \(startup_32\|startup_64\|efi32_stub_entry\|efi64_stub_entry\|efi_pe_entry\|efi32_pe_entry\|efi_boot_params\|input_data\|kernel_info\|_end\|_ehead\|_text\|_data\|z_.*\)$$/\#define ZO_\2 0x\1/p'quiet_cmd_zoffset = ZOFFSET $@ cmd_zoffset = $(NM) $< | sed -n $(sed-zoffset) > $@Quoted 3 lines
arch/x86/boot/tools/build.c +0
-0PARSE_ZOFS (p, _end); p =strchr (p,'\n' );
Ard Biesheuvel
maintainerQuoted 59 lines · Evgeniy Baskov
Quoted 40 lines · Ard Biesheuvel
This is a follow-up to work proposed by Evgeny to tighten memory permissions used by the EFI stub and subsequently by the decompressor on
x86.Instead of going out of our way to make more space in the first 500 bytes of the image, and relying on non-1:1 mapped sections (which is risky in the context of bespoke PE loaders), these patches reorganize the header so the PE header comes after the x86 setup header, and can be
extended at will.I pushed a branch at [1] that combines this with v4 of Evgeny's series (after some minor surgery, e.g., to reorder the text and rodata sections
so they are contiguous)We might split off the rodata section as well, and give it read/non-exec
permissions, but I'd like to discuss the approach first, and perhaps get
some testing data points.Cc Evgeniy Baskov <[email protected]>Cc Borislav Petkov <[email protected]>Cc Alexey Khoroshilov <[email protected]>Cc Peter Jones <[email protected]>Cc "Limonciello, Mario" <[email protected]>[0]
https://lore.kernel.org/linux-efi/[email protected]/
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-x86-nx-v4Ard Biesheuvel (4):
efi: x86: Use private copy of structsetup_header
efi: x86: Move PE header after setup header
efi: x86: Drop alignment section header flags
efi: x86: Split PE/COFF .text section into .text and .dataQuoted 6 lines
arch/x86/boot/Makefile | 2 +- arch/x86/boot/header.S | 52 +++++++++----------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 38 +++++++++----- drivers/firmware/efi/libstub/x86-stub.c | 43 +++------------- 5 files changed, 59 insertions(+), 77 deletions(-)I've quickly looked through these patches but I'll do more testing tomorrow.
This approach seems to be better than mine if it will work. I've tried the similar thing but I did not think of creating the local copy of the bootparams and the attempt to map them did not work since the PE loader I am trying to get kernel booting with does not accept sections before the PE header. But since the bootparams is inside the padding and is not used, it should be fine.
Quoted 7 lines
But this will still need more changes to work properly with stricter PE loaders like the one that I've mentioned in my patch series [1].
The image should also have 4K aligned section virtual addresses and sizes
(even on .reloc and .compat AFAIK), otherwise UEFI will ignore memory attributes (or refuse to load the kernel).
EDK2 works fine as is, i.e. with only .text and .data aligned to 4k virtually, and the data size of .data aligned to 512 bytes.
ProtectUefiImageCommon - 0x3C8600C0
- 0x0000000038777000 - 0x0000000002BC6000
SetUefiImageMemoryAttributes - 0x0000000038777000 - 0x0000000000004000 (0x0000000000004008)
SetUefiImageMemoryAttributes - 0x000000003877B000 - 0x0000000000BEE000 (0x0000000000020008)
SetUefiImageMemoryAttributes - 0x0000000039369000 - 0x0000000001FD4000 (0x0000000000004008)
Quoted 4 lines
Another desired thing is
having
adjacent section with no padding in between them, since [1] does have a mode that requires sections them to be adjacent.
Does that have any basis in the PE/COFF spec?
Quoted 4 lines
(SizeOfHeaders/header_size
should also be set to the size of setup since it is also checked to be adjacent to the first section.)
Does that have any basis in the PE/COFF spec?
Quoted 6 lines
I did not do the one-to-one mapping of file and virtual addresses since it
would require almost 4K paddings for the auxiliary sections.
I've backpedaled a little bit from this approach (see my other comment).
If we just rip out the real mode stub, we can keep the PE header before the setup header, and simply describe whatever comes as .text.
Quoted 71 lines · Ard Biesheuvel
Quoted 59 lines · Evgeniy Baskov
Quoted 40 lines · Ard Biesheuvel
This is a follow-up to work proposed by Evgeny to tighten memory permissions used by the EFI stub and subsequently by the decompressor on
x86.Instead of going out of our way to make more space in the first 500 bytes of the image, and relying on non-1:1 mapped sections (which is risky in the context of bespoke PE loaders), these patches reorganize the header so the PE header comes after the x86 setup header, and can be
extended at will.I pushed a branch at [1] that combines this with v4 of Evgeny's series (after some minor surgery, e.g., to reorder the text and rodata sections
so they are contiguous)We might split off the rodata section as well, and give it read/non-exec
permissions, but I'd like to discuss the approach first, and perhaps get
some testing data points.Cc Evgeniy Baskov <[email protected]>Cc Borislav Petkov <[email protected]>Cc Alexey Khoroshilov <[email protected]>Cc Peter Jones <[email protected]>Cc "Limonciello, Mario" <[email protected]>[0]
https://lore.kernel.org/linux-efi/[email protected]/
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=efi-x86-nx-v4Ard Biesheuvel (4):
efi: x86: Use private copy of structsetup_header
efi: x86: Move PE header after setup header
efi: x86: Drop alignment section header flags
efi: x86: Split PE/COFF .text section into .text and .dataQuoted 6 lines
arch/x86/boot/Makefile | 2 +- arch/x86/boot/header.S | 52 +++++++++----------- arch/x86/boot/setup.ld | 1 + arch/x86/boot/tools/build.c | 38 +++++++++----- drivers/firmware/efi/libstub/x86-stub.c | 43 +++------------- 5 files changed, 59 insertions(+), 77 deletions(-)I've quickly looked through these patches but I'll do more testing tomorrow.
This approach seems to be better than mine if it will work. I've tried the similar thing but I did not think of creating the local copy of the bootparams and the attempt to map them did not work since the PE loader I am trying to get kernel booting with does not accept sections before the PE header. But since the bootparams is inside the padding and is not used, it should be fine.
Quoted 7 lines
But this will still need more changes to work properly with stricter PE loaders like the one that I've mentioned in my patch series [1].
The image should also have 4K aligned section virtual addresses and sizes
(even on .reloc and .compat AFAIK), otherwise UEFI will ignore memory attributes (or refuse to load the kernel).EDK2 works fine as is, i.e. with only .text and .data aligned to 4k virtually, and the data size of .data aligned to 512 bytes.
Quoted 9 lines
ProtectUefiImageCommon -
0x3C8600C0
-0x0000000038777000-0x0000000002BC6000
SetUefiImageMemoryAttributes -0x0000000038777000-0x0000000000004000(0x0000000000004008)
SetUefiImageMemoryAttributes -0x000000003877B000-0x0000000000BEE000(0x0000000000020008)
SetUefiImageMemoryAttributes -0x0000000039369000-0x0000000001FD4000(0x0000000000004008)
Nice to know that. I think .reloc and .compat can be kept small, since protection for compressed kernel image is getting applied manually anyways (patch "efi/x86: Explicitly set sections memory attributes"). But anyways we can align text/data on 4K by rounding setup size (or the headers size if setup gets ripped out):
arch/x86/boot/tools/build.c +0 -0
@@@ -502,9 -502,9 +505,11 @@@ static unsigned int read_setup(char *pa file_size +=reserve_pecoff_compat_section (file_size); file_size +=reserve_pecoff_reloc_section (file_size);
-- /* Pad unused space with zeros */
--
++#ifdef CONFIG_EFI_STUB
++ setup_size = round_up(file_size, 0x1000);
++#else
setup_size = round_up(file_size, SECTOR_SIZE);
++#endif
if (setup_size < SETUP_SECT_MIN * SECTOR_SIZE) setup_size = SETUP_SECT_MIN * SECTOR_SIZE;
Quoted 6 lines
Quoted 4 lines
Another desired thing is
having
adjacent section with no padding in between them, since [1] does have a mode that requires sections them to be adjacent.Does that have any basis in the PE/COFF spec?
No, it is not, I think this mode is rather for the internal firmware images. So this would just be nice to have and nothing strongly required.
Quoted 7 lines
Quoted 5 lines
(SizeOfHeaders/header_size
should also be set to the size of setup since it is also checked to be adjacent to the first section.)Does that have any basis in the PE/COFF spec?
This is neither.
Quoted 5 lines
Quoted 5 lines
I did not do the one-to-one mapping of file and virtual addresses since it
would require almost 4K paddings for the auxiliary sections.
Quoted 7 lines
Quoted 2 lines
I've backpedaled a little bit from this approach (see my other comment).
If we just rip out the real mode stub, we can keep the PE header before the setup header, and simply describe whatever comes as .text.
That sounds promising. I think the safest way is to make this a compile time option though, at least as the initial change, so it will not break any obscure boot loaders. But since modern kernel configurations are likely won't even fit into the real mode address space, this option can probably be made mutually exclusive with EFISTUB or CONFIG_EFI_DXE_MEM_ATTRIBUTES.
Thanks,
Evgeniy Baskov