Linux Kernel Control-Flow Integrity Sup...
summary
Kernel CFI uses compiler‑emitted type tags: a 32‑bit type hash before function entry and a matching check just before each indirect call, with a traps on mismatch policy that can be made permissive for warnings. ARM and x86 offer hardware IBT/IBT‑like enforcement that can be combined with compiler checks by hot‑patching fineIBT to target bytes before entry, avoiding executable memory reads, improving speculative hardening and easing relaxed‑target handling. Clang support is upstreaming; GCC work is pending.
AI-written summary · about
chapters (4)
- 0:00Start
- 14:57KCFI instrumentation
- 18:06ARM Branch Target Identification (BTI)
- 28:12IBT instrumentation
related talks
45mControl Flow Integrity in the Linux Kernel
39mControl Flow Integrity in the Linux Kernel
27mFiner-grained kernel control flow integrity and challenges
01h 46mA little Introduction to Control Flow Integrity
58mFineIBT Enhanced: Hardening Linux’s Microarchitectural Security on X86
35mControl Flow Integrity on RISC-V Linux
01h 34mA Little Introduction to Control Flow Integrity in C++
20mControl Flow Integrity on RISCV
