diff options
author | Peter Zijlstra <peterz@infradead.org> | 2023-06-15 22:35:48 +0300 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2023-07-10 10:52:25 +0300 |
commit | 04505bbbbb15da950ea0239e328a76a3ad2376e0 (patch) | |
tree | bd85fe01301497d709a8d33ad012e960310c57ea /scripts/gdb/linux/utils.py | |
parent | 3aec4ecb3d1f313a8ab985df7cab07c4af81f478 (diff) | |
download | linux-04505bbbbb15da950ea0239e328a76a3ad2376e0.tar.xz |
x86/fineibt: Poison ENDBR at +0
Alyssa noticed that when building the kernel with CFI_CLANG+IBT and
booting on IBT enabled hardware to obtain FineIBT, the indirect
functions look like:
__cfi_foo:
endbr64
subl $hash, %r10d
jz 1f
ud2
nop
1:
foo:
endbr64
This is because the compiler generates code for kCFI+IBT. In that case
the caller does the hash check and will jump to +0, so there must be
an ENDBR there. The compiler doesn't know about FineIBT at all; also
it is possible to actually use kCFI+IBT when booting with 'cfi=kcfi'
on IBT enabled hardware.
Having this second ENDBR however makes it possible to elide the CFI
check. Therefore, we should poison this second ENDBR when switching to
FineIBT mode.
Fixes: 931ab63664f0 ("x86/ibt: Implement FineIBT")
Reported-by: "Milburn, Alyssa" <alyssa.milburn@intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Sami Tolvanen <samitolvanen@google.com>
Link: https://lore.kernel.org/r/20230615193722.194131053@infradead.org
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions