summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2023-03-10 13:30:05 +0100
committerArd Biesheuvel <ardb@kernel.org>2023-03-10 14:11:40 +0100
commit3c66bb1918c262dd52fb4221a8d372619c5da70a (patch)
treea338570fb7dae773c444f3d22870b8f177e31c95 /include
parentefi/libstub: arm64: Remap relocated image with strict permissions (diff)
downloadlinux-3c66bb1918c262dd52fb4221a8d372619c5da70a.tar.xz
linux-3c66bb1918c262dd52fb4221a8d372619c5da70a.zip
arm64: efi: Set NX compat flag in PE/COFF header
The PE/COFF header has a NX compat flag which informs the firmware that the application does not rely on memory regions being mapped with both executable and writable permissions at the same time. This is typically used by the firmware to decide whether it can set the NX attribute on all allocations it returns, but going forward, it may be used to enforce a policy that only permits applications with the NX flag set to be loaded to begin wiht in some configurations, e.g., when Secure Boot is in effect. Even though the arm64 version of the EFI stub may relocate the kernel before executing it, it always did so after disabling the MMU, and so we were always in line with what the NX compat flag conveys, we just never bothered to set it. So let's set the flag now. Cc: <stable@vger.kernel.org> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions