SEC.co Podcast

Containers promise isolation — but a shared kernel can shatter that promise. This episode breaks down how attackers exploit kernel modules to escape containers entirely, and what defenders must do to close the gap.

Show Notes

Container security is often treated as a solved problem — namespaces, cgroups, and image hardening give teams confidence that workloads are properly isolated. But that confidence has a critical blind spot: every container on a host shares the same kernel. This episode of Cybersecurity examines one of the most dangerous exploitation paths in modern infrastructure — container escape via kernel modules — drawing on this in-depth breakdown of real-world container escape exploits and risks from the SEC research team.
The episode walks through the full attack chain — from initial foothold to full host compromise — and explores the misconfigurations that make it possible. Here's what's covered:
  • Why containers aren't virtual machines: Unlike VMs, containers share the host kernel, meaning kernel-level access is never truly off the table for a determined attacker.
  • What kernel modules are and why they're dangerous: Modules run at the deepest privilege level of the system — if an attacker loads a malicious one, they effectively own the host, not just the container.
  • How the attack chain unfolds: From exploiting a vulnerable application inside a container, through privilege escalation (often aided by containers running as root), to abusing the CAP_SYS_MODULE capability to load a hostile kernel module.
  • Why detection is so difficult: Malicious kernel-level code runs beneath standard monitoring tools and can disable audit logging, hide processes, and intercept system calls before any alert fires.
  • The four conditions attackers depend on: Containers running as root, overly permissive Linux capabilities, absent or misconfigured mandatory access controls (SELinux/AppArmor), and unpatched kernels with known CVEs.
  • Practical defenses that actually reduce the attack surface: Enforcing least privilege, stripping CAP_SYS_MODULE from production containers, disabling dynamic module loading at the host level, patching kernels with the same urgency as application dependencies, and investing in sub-user-space monitoring.
The episode closes with a reminder that none of these defenses are exotic — they're foundational practices. The gap between a secure container environment and a compromised one is often a handful of configuration decisions made for convenience rather than security. For more from the show on related cloud infrastructure risk, listen to Cloud Misconfigurations: Why They're Still the #1 Cause of Breaches.
SEC

What is SEC.co Podcast ?

A podcast about latest trends, techniques and learnings in cybersecurity and cyberdefense.