The vulnerability arises from KubeVirt's safepath package where the OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descriptor to a path leaf, but subsequent operations resolve the path via /proc/self/fd/N using link-following syscalls. When the leaf is a symlink, the kernel dereferences it, 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. These events are processed without validation and propagated to the Kubernetes API, allowing the attacker to trigger incorrect VM lifecycle actions, corrupt VMI resource state, or crash the virt-handler process. Since 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 file ownership or permission changes to arbitrary host files, though this is limited by SELinux and immutable filesystem layers in default deployments. No mitigation currently prevents the notify socket hijacking vector. The CVSS v3.1 score is 7.3 (High) with vector AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H.

An attacker with access to a virt-launcher pod can hijack virt-handler's IPC notify socket, injecting arbitrary VM lifecycle events that cause incorrect VM actions (shutdown, restart, migration), corrupt VM state in the Kubernetes API, or crash virt-handler. Crashing virt-handler repeatedly results in denial of VM management services on the affected node, impacting all virtual machines there. Additionally, the attacker can cause virt-handler to change file ownership or permissions on unintended host paths, though this impact is limited by SELinux and immutable filesystem protections. Confidentiality is not impacted, but integrity is low and availability impact is high.

Red Hat recommends reviewing and restricting RBAC policies to limit pod and exec permissions on virt-launcher pods to only necessary users, reducing the attacker pool able to place symlinks. Ensure SELinux is in enforcing mode to restrict file targets for ownership and permission changes. Immutable filesystem layers in RHCOS also limit modification of core OS files. Note that no current mitigation fully addresses the notify socket hijacking vector, which remains exploitable despite SELinux and filesystem immutability. Applying the vendor-provided updates in OpenShift Virtualization v4.22 images is advised once available. Monitor Red Hat advisories for official patches and updates.