Exploit Methods/Kernel location

From Linux Kernel Security Subsystem
Revision as of 22:54, 4 November 2015 by KeesCook (talk | contribs) (Created page with "= Details = Finding the kernel location can be an important first step for exploitation. Without it, for example, it's harder to make kernel function calls for privilege escal...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Details

Finding the kernel location can be an important first step for exploitation. Without it, for example, it's harder to make kernel function calls for privilege escalation. Besides the kernel itself, lots of other locations may be valuable to an attacker. See [Bug Classes/Kernel pointer leak|Kernel pointer leaks] for more information.

Examples

Mitigations

  • hide symbols and kernel pointers (see Kernel pointer leaks)
  • [kernel ASLR]
  • runtime randomization of kernel functions
  • executable-but-not-readable memory
  • per-build structure layout randomization (e.g. GRKERNSEC_RANDSTRUCT)