Control-flow integrity
A runtime exploit mitigation that constrains a program's indirect jumps and calls to valid targets, blocking control-flow hijacking even when a memory-corruption bug like a use-after-free is present.
grounded in: Trend: a 15-year-old stack use-after-free across all Linux distros, illustrating latent memory-corruption bugs that mitigations like CFI are designed to contain.
Connected concepts
Memory safety, Use-after-free, Sandbox escape, Trusted Computing Base
Explore it live in the knowledge graph →