The vulnerability arises from the OpenAtNoFollow function in KubeVirt's safepath package, which uses O_PATH|O_NOFOLLOW to get a file descriptor to a path leaf. However, subsequent operations resolve the path via /proc/self/fd/N using link-following syscalls, causing the kernel to dereference symlinks and bypass the intended 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 lifecycle actions (shutdowns, restarts, migrations), corrupt VMI resource state, or crash the virt-handler process. Because virt-handler runs as a single DaemonSet pod per node, repeated crashes cause denial of VM management services for all VMs on that node. A secondary impact allows virt-handler, running as root, to apply chown/chmod operations to arbitrary host files, but this is limited by SELinux enforcing mode and RHCOS immutable filesystem layers in default OpenShift Virtualization deployments. No current mitigation addresses the notify socket hijacking vector.

The vulnerability allows an attacker with low privileges (access to a virt-launcher pod) to hijack IPC socket connections used by virt-handler, leading to injection of arbitrary VM lifecycle events. This can cause incorrect VM lifecycle actions, corruption of VM state in Kubernetes API, or crashes of the virt-handler process. Sustained crashes result in denial of VM management services on the affected node, impacting all virtual machines hosted there. Additionally, the attacker can cause unintended file ownership or permission changes on host files, though this impact is limited by SELinux and immutable filesystem protections. Confidentiality is not impacted, but integrity is low and availability impact is high.

No mitigation currently addresses the notify socket hijacking vector. Recommended measures include reviewing and restricting RBAC policies to limit pod and exec permissions on virt-launcher pods to only necessary users, reducing the attacker pool. Ensure SELinux is in enforcing mode to limit the set of host files targetable via the chown/chmod path. RHCOS immutable filesystem layers also help prevent modification of core OS files. Users should monitor Red Hat advisories for any forthcoming patches or updates addressing this issue.