What Happened
Google Cloud published bulletin GCP-2026-078 for CVE-2026-98432, a GKE container escape vulnerability in the Linux kernel IPv4 TCP stack. The flaw can cause a kernel panic or a container escape, which means root code execution on the node. Google Cloud states that GKE Standard clusters and GKE Autopilot clusters are impacted.
Google Cloud rated the issue Medium. Fortinet PSIRT lists a CVSSv3 score of 9.8 for the same CVE, and Sophos lists severity High. Ratings differ between vendors on kernel memory bugs, so treat the score as a starting point and your exposure as the deciding factor.
For an MSP the practical question is narrow. Which clients run GKE Standard or Autopilot, and can anything outside a trusted source reach a TCP listener on those nodes, Pods or control plane endpoint?
A kernel panic takes a node down, and the workloads on it restart. A container escape is worse, because the attacker gets root on the node. From there the node's identity and the credentials it carries become the problem. In general, node level compromise is a credential incident as much as a workload incident, because the node holds what the pods were given.
Timeline
- 2026-11-02: Fortinet PSIRT published advisory FG-IR-26-188, Linux kernel RCE CVE-2026-98432, listing a CVSSv3 score of 9.8. Sophos also first published its advisory on this date.
- 2026-11-04: Google Cloud published bulletin GCP-2026-078, stating that the flaw is in the Linux kernel IPv4 TCP stack and that GKE Standard and GKE Autopilot clusters are impacted. Google Cloud rated it Medium.
- 2026-11-18: Google Cloud updated the bulletin and added patch versions for GKE.
- 2026-11-19: Ubuntu Security published USN-9170-1, USN-9171-1, USN-9172-1, USN-9170-2 and USN-9171-2, listing CVE-2026-98432 among the kernel flaws corrected.
- 2026-11-20: Ubuntu Security published USN-9170-3 and USN-9184-1. Sophos updated its advisory on this date.
Who Is Affected
Google Cloud states that GKE Standard clusters and GKE Autopilot clusters are impacted, and that the vulnerability sits in the Linux kernel IPv4 TCP stack. That covers any MSP running either cluster type for a client.
Ubuntu Security published kernel update notices that list CVE-2026-98432: USN-9170-1, USN-9171-1, USN-9172-1, USN-9170-2, USN-9171-2, USN-9170-3 and USN-9184-1. The notices cover IPv4 networking among other subsystems, and some are for AWS FIPS, Oracle and NVIDIA Tegra IGX kernels. If you maintain Ubuntu hosts that run container workloads, those hosts are in scope.
Google Cloud states that clusters which restrict access to trusted sources, for example with firewall rules and control plane authorized networks, are not exposed to network attacks. The local trigger from inside a container still applies, so a closed network path does not remove the need to patch.
Why The GKE Container Escape Vulnerability Matters To MSPs
Kubernetes nodes are shared. One node often runs workloads for more than one client, so a container escape is not contained to the client whose container started it. Root on a node reaches the kubelet credentials and the service account tokens the node holds, and that is how a single workload becomes a cluster problem.
Kernel updates are the step that gets postponed. Cluster upgrades and workload changes get attention because they show up in a change board. The kernel underneath them often does not, especially on managed clusters that an MSP does not build itself. As a standing practice, an MSP should know who owns kernel patching on every platform it runs, and should be able to prove the patch landed.
There is also a timing problem. Network reachability is often wider than it should be. In general, control plane endpoints and node listeners stay open to broad source ranges because closing them breaks someone's tooling, and nobody owns the decision to close them.
Technical Details
The CVE is CVE-2026-98432. Google Cloud describes it as a vulnerability in the Linux kernel IPv4 TCP stack. The affected products named in the sources are GKE Standard clusters and GKE Autopilot clusters, and the Linux kernel IPv4 TCP stack itself.
Attack vector, as Google Cloud states it: an unprivileged process in a container can trigger it locally, without special capabilities such as CAP_NET_RAW. A network attacker can also trigger it by sending TCP packets with IPv4 options to a listener on the node or on the cluster control plane. The network attack requires access to a TCP listener on your nodes, Pods, or the control plane's IP-based endpoint.
Fortinet PSIRT describes the flaw as freeing inet_opt and ireq_opt after an RCU grace period. It states that tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the child socket without copying it, and that inet_sock_destruct() frees inet_opt with a plain kfree(), which leads to a use-after-free in ip_options_build(). Fortinet states that IPv6 is not affected by the first issue, because tcp_v6_syn_recv_sock() duplicates the options.
On versions: Google Cloud's 2026-11-18 update added patch versions for GKE, and the bulletin points to the GKE security bulletin for the versions and the instructions. No specific version numbers appear in the material behind this advisory.
On severity: Google Cloud rates the issue Medium. Sophos lists severity High. Fortinet PSIRT lists a CVSSv3 score of 9.8. Google Cloud states the issue had not been exploited at the time of publication, and no source reports exploitation in the wild.
What MSPs Should Do
Start with exposure, then patch. The network trigger is the part you can close today, and it is the part that decides which clusters are urgent.
- Build the list. Write down every client on GKE Standard or GKE Autopilot, with cluster names, owners and the business service each one runs.
- Apply the GKE patch versions listed in the GKE security bulletin.
- Restrict access to TCP listeners on nodes, Pods and the control plane endpoint to trusted sources using firewall rules and control plane authorized networks.
- Patch the Ubuntu kernels that USN-9170-1, USN-9171-1, USN-9172-1, USN-9170-2, USN-9171-2, USN-9170-3 and USN-9184-1 cover, including the AWS FIPS, Oracle and NVIDIA Tegra IGX variants where you run them.
- Confirm each patched host is actually running the new kernel, and reboot where the update requires it.
- As a standing practice, check for signs of node level compromise: unexpected processes or containers, new privileged pods, and outbound connections that do not match the workload.
- Check that anything running on those clusters can be restored without the cluster. That means a backup you can read, and a restore path you have tested.
- Tell the client what changed and when, in one short message. They will ask, and a clear answer is cheaper than a status meeting later.
How EnterProtect Helps
Kernel and platform bugs are a reminder that patching is one control and recovery is another. EnterProtect backup keeps clean, restorable copies of the systems your clients depend on, held separately from the environment they run in. If a node is lost, or a cluster has to be rebuilt, you are not starting from whatever survived the incident.
EnterProtect recovery gets a client running again. That matters most when the failure is infrastructure rather than data: a crashed node, a rebuilt cluster, a workload that has to be stood up somewhere else while the original is cleaned up.
EnterProtect vulnerability scanning gives you a standing view of which systems in a client environment are behind on updates, so exposure is something you can see between incidents rather than something you discover during one.
This advisory describes a kernel flaw. EnterProtect does not detect, block or prevent this attack. The work of patching and restricting access is yours, and the bulletins tell you how to do it.
Frequently Asked Questions
What Is CVE-2026-98432?
CVE-2026-98432 is a vulnerability in the Linux kernel IPv4 TCP stack. Google Cloud states it can cause a kernel panic or a container escape, which means root code execution on the node. Google published it in bulletin GCP-2026-078 and rated it Medium.
Can CVE-2026-98432 Escape a Container?
Yes. Google Cloud states the flaw can cause a container escape that results in root code execution on the node. The same bulletin says an unprivileged process inside a container can trigger it locally without special capabilities such as CAP_NET_RAW. A network attacker can trigger it by sending TCP packets with IPv4 options to a listener on the node or on the cluster control plane.
Which GKE Clusters Are Affected?
Google Cloud states that GKE Standard clusters and GKE Autopilot clusters are impacted. The flaw itself is in the Linux kernel IPv4 TCP stack. Google Cloud also states that clusters which restrict access to trusted sources, for example with firewall rules and control plane authorized networks, are not exposed to network attacks.
Is CVE-2026-98432 Being Exploited in the Wild?
No source in this story reports exploitation in the wild. Google Cloud published the bulletin on 2026-11-04 and updated it on 2026-11-18 with patch versions for GKE. The absence of reported exploitation is not a reason to delay patching, since the network trigger needs only access to a reachable TCP listener.
What Should an MSP Do First About CVE-2026-98432?
Find out which clients run GKE Standard or GKE Autopilot, then restrict access to TCP listeners on nodes, Pods and the control plane endpoint to trusted sources using firewall rules and control plane authorized networks. Apply the GKE patch versions listed in the GKE security bulletin. Ubuntu Security also published kernel notices listing this CVE for Ubuntu kernels.
Does Restricting Network Access to My Cluster Reduce the Risk?
It removes the network path to the bug. Google Cloud states that the network attack requires access to a TCP listener on your nodes, Pods, or the control plane's IP-based endpoint, and that clusters restricting this access to trusted sources with firewall rules and control plane authorized networks are not exposed to network attacks. The local trigger from inside a container is not closed by network rules, so patching is still required.
Sources
- Linux kernel RCE CVE-2026-98432 (Fortinet Psirt)
- USN-9170-1: Linux kernel vulnerabilities (Ubuntu Security)
- USN-9171-1: Linux kernel vulnerabilities (Ubuntu Security)
- USN-9172-1: Linux kernel vulnerabilities (Ubuntu Security)
- USN-9170-2: Linux kernel (AWS FIPS) vulnerabilities (Ubuntu Security)
- USN-9171-2: Linux kernel (Oracle) vulnerabilities (Ubuntu Security)
- Advisory: Linux Kernel TCP Vulnerability (CVE-2026-98432) (Sophos Psirt Feed)
- USN-9170-3: Linux kernel (Oracle) vulnerabilities (Ubuntu Security)
- USN-9184-1: Linux kernel (NVIDIA Tegra IGX) vulnerabilities (Ubuntu Security)
- GCP-2026-078 (Google Cloud Security Corrected)