A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Link | Tags |
|---|---|
| https://github.com/kubernetes/kubernetes/issues/126587 | vendor advisory issue tracking |
| https://groups.google.com/g/kubernetes-security-announce/c/67D7UFqiPRc | mailing list |
| http://www.openwall.com/lists/oss-security/2025/03/20/2 |