diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2025-04-12 13:56:01 +0200 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2025-08-18 14:23:09 +0200 |
| commit | 894af4a1cde61c3401f237184fb770f72ff12df8 (patch) | |
| tree | 6b00452a8bbc9e38b6d4578cf5990c19911724a0 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | x86/fred: KVM: VMX: Always use FRED for IRQs when CONFIG_X86_FRED=y (diff) | |
| download | linux-894af4a1cde61c3401f237184fb770f72ff12df8.tar.gz linux-894af4a1cde61c3401f237184fb770f72ff12df8.zip | |
objtool: Validate kCFI calls
Validate that all indirect calls adhere to kCFI rules. Notably doing
nocfi indirect call to a cfi function is broken.
Apparently some Rust 'core' code violates this and explodes when ran
with FineIBT.
All the ANNOTATE_NOCFI_SYM sites are prime targets for attackers.
- runtime EFI is especially henous because it also needs to disable
IBT. Basically calling unknown code without CFI protection at
runtime is a massice security issue.
- Kexec image handover; if you can exploit this, you get to keep it :-)
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Josh Poimboeuf <jpoimboe@kernel.org>
Acked-by: Sean Christopherson <seanjc@google.com>
Link: https://lkml.kernel.org/r/20250714103441.496787279@infradead.org
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions