The vulnerability (CVE-2026-13201) exists in KubeVirt's safepath package used by virt-handler. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW flags to obtain a file descriptor to a path leaf, intending to avoid following symlinks. However, downstream operations resolve the path via /proc/self/fd/N, which dereferences symlinks, defeating the no-follow protection. An attacker with access to a virt-launcher pod can replace the notify socket path with a symlink to an attacker-controlled socket, enabling injection of arbitrary VM domain lifecycle events into virt-handler. Since virt-handler trusts this IPC channel, injected events can cause incorrect VM lifecycle actions, corrupt VM state in the Kubernetes API, or crash virt-handler, resulting in denial of VM management services on the node. A secondary impact allows virt-handler, running as root, to apply file ownership or permission changes to unintended host files, though this is limited by SELinux enforcing mode and immutable filesystem layers in default OpenShift Virtualization deployments.

The primary impact is hijacking of the notify socket used by virt-handler, enabling injection of arbitrary VM lifecycle events without validation. This can cause incorrect VM lifecycle actions such as shutdowns, restarts, or migrations, corrupt VM instance resource state in the Kubernetes API, or crash the virt-handler process. Because virt-handler runs as a single DaemonSet pod per node, a crash loop causes sustained denial of VM management services for all VMs on that node, including console access and live migration. The secondary impact is unauthorized file ownership or permission changes on host files by virt-handler running as root, but this is constrained by SELinux enforcing mode and immutable filesystem layers in default OpenShift deployments. The attacker cannot read or write file contents and remains confined to the container.

No fix is currently available for the notify socket hijacking vector. Mitigation focuses on reducing the attacker pool and limiting secondary impact by reviewing and restricting RBAC policies to limit pod and exec permissions on virt-launcher pods to only necessary users. Ensure SELinux is in enforcing mode to restrict file targets for chown/chmod operations. Immutable filesystem layers in RHCOS prevent modification of core OS files. Note that SELinux and filesystem immutability do not prevent notify socket hijacking. Monitor Red Hat advisories for updates and apply patches when released.