Kernel exploits target vulnerabilities in the Linux kernel itself. They're the "nuclear option" - if successful, you get root regardless of any other security controls. But they're risky and should be a last resort.
Think of kernel exploits like hacking the building's foundation. You bypass all the locks, guards, and cameras by exploiting a flaw in the very structure everything sits on. Powerful, but you might also bring down the whole building.
System Stability Risk
Kernel exploits can crash the system. In CTFs, this loses your shell. In real engagements, this alerts defenders. Always try other methods first (sudo, SUID, cron, etc.) before attempting kernel exploits.
Gathering Kernel Information
Version Precision
Kernel exploits are version-specific. 4.15.0-142 might be vulnerable, but 4.15.0-143 might not. Record the EXACT version string.
Searching for Exploits
Searchsploit
Linux Exploit Suggester
Online Resources
Famous Kernel CVEs
Evaluating Exploits
Quick Vulnerability Checks
Kernel Enumeration Methodology
Kernel Exploit Research Flow
1
Get Versionuname -r for exact kernel version
2
Distributioncat /etc/os-release for distro
3
Architectureuname -m for 32/64 bit
4
SuggesterRun linux-exploit-suggester
5
Searchsearchsploit for version matches
6
EvaluateRead exploit requirements carefully
Knowledge Check
Challenges
Key Takeaways
- Record exact kernel version with uname -r
- Note architecture (x86_64 vs i686) for exploit compatibility
- Use linux-exploit-suggester for automated vulnerability detection
- searchsploit is essential for finding exploit code
- Always evaluate exploits before running (version match, requirements)
- Kernel exploits should be last resort due to crash risk