diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2023-01-09 10:44:31 +0100 |
---|---|---|
committer | Ard Biesheuvel <ardb@kernel.org> | 2023-01-13 17:15:17 +0100 |
commit | d3f450533bbcb6dd4d7d59cadc9b61b7321e4ac1 (patch) | |
tree | 352be162e2481bec043a3858fa7a4f917bde998e /arch | |
parent | 18bba1843fc7f264f58c9345d00827d082f9c558 (diff) | |
download | linux-stable-d3f450533bbcb6dd4d7d59cadc9b61b7321e4ac1.tar.gz linux-stable-d3f450533bbcb6dd4d7d59cadc9b61b7321e4ac1.tar.bz2 linux-stable-d3f450533bbcb6dd4d7d59cadc9b61b7321e4ac1.zip |
efi: tpm: Avoid READ_ONCE() for accessing the event log
Nathan reports that recent kernels built with LTO will crash when doing
EFI boot using Fedora's GRUB and SHIM. The culprit turns out to be a
misaligned load from the TPM event log, which is annotated with
READ_ONCE(), and under LTO, this gets translated into a LDAR instruction
which does not tolerate misaligned accesses.
Interestingly, this does not happen when booting the same kernel
straight from the UEFI shell, and so the fact that the event log may
appear misaligned in memory may be caused by a bug in GRUB or SHIM.
However, using READ_ONCE() to access firmware tables is slightly unusual
in any case, and here, we only need to ensure that 'event' is not
dereferenced again after it gets unmapped, but this is already taken
care of by the implicit barrier() semantics of the early_memunmap()
call.
Cc: <stable@vger.kernel.org>
Cc: Peter Jones <pjones@redhat.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Reported-by: Nathan Chancellor <nathan@kernel.org>
Tested-by: Nathan Chancellor <nathan@kernel.org>
Link: https://github.com/ClangBuiltLinux/linux/issues/1782
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions