Lead story
An 18-Year-Old Linux Bug Let Attackers Escape Containers and Own the Host — It's Fixed Now, But Patch Fast
A use-after-free vulnerability hiding in the Linux kernel's SCTP networking stack since 2008 has been confirmed exploitable — and Tencent researchers have now demonstrated a working exploit that escapes a container and lands root access on the underlying host. The flaw, disclosed this week, is the kind of "it's been there the whole time" bug that makes anyone running containerised workloads quietly reconsider their weekend plans.
What is SCTP and why does this matter?
SCTP (Stream Control Transmission Protocol) is an alternative to TCP primarily used in telecoms, some cloud-native workloads, and high-availability networking. It's not as ubiquitous as TCP, but it's enabled by default in many Linux distributions — meaning a lot of systems have the vulnerable code loaded even if they're not actively using the protocol.
The use-after-free bug allows an attacker who can reach the SCTP stack to corrupt kernel memory. Tencent's researchers went further than disclosing the primitive: they turned it into a container escape, meaning code running inside a Docker or similar container can break out and execute with full root privileges on the host machine. In cloud and Kubernetes environments — including the managed container platforms widely used by Australian enterprises and government agencies — that's a worst-case scenario.
The fix is out, but the window is real
Stable kernel releases 7.1.6, 6.18.42, 6.12.101, and 6.6.148 (all shipped on 3 August) contain the patch. If you're running a kernel older than those on a system where SCTP is reachable — from within a container, from the network, or from an unprivileged local user — you're exposed. The good news is that most major Linux distributions have already pushed updated packages; the bad news is that patching kernel versions in production, especially in Kubernetes clusters, requires care and often a maintenance window.
Who should act now
If you run containerised workloads on Linux and haven't applied the August kernel updates, that's the immediate action item. Security teams operating under Australia's SOCI Act — particularly those in critical infrastructure sectors using containerised environments — should treat this as a high-priority patch given the container-escape demonstration. For everyone else: check whether your cloud provider's managed Kubernetes offering has applied the fix automatically, but don't assume.
The bigger picture
This lands in the middle of Black Hat USA 2026 week, which has produced an unusually dense cluster of novel research — the NatJack NAT-hijacking attack, MIT's TONTOU bypass of Spectre mitigations, and PortSwigger's AI-assisted HTTP desync work all dropped in the same 48 hours. Defenders are being asked to absorb a lot at once.
The 18-year lifespan of this flaw is a reminder that complex kernel code accumulates risk quietly. SCTP in particular has had a chequered security history. It won't be the last old bug to surface — but it's now one fewer to worry about, provided you patch.
What to watch: whether cloud providers issue explicit advisories about their managed Kubernetes kernel update status, and whether this surfaces as an active exploitation indicator in the coming weeks.
