The bug in the Linux kernel's WireGuard network namespace cleanup path introduces a deadlock by manually acquiring the rtnl_lock during the .pre_exit callback. This locking strategy causes any thread holding the rtnl_mutex—such as the cleanup_net workqueue or rollback paths—to block indefinitely, leading to a hung task. The result is a denial-of-service condition that can stall kernel operations within the affected namespace, potentially affecting system responsiveness or availability.

The vulnerability applies to the Linux kernel, affecting all distributions that ship the kernel code unchanged and lack the patch that replaces the manual rtnl_lock with the .exit_rtnl hook introduced in commit 7a60d91c690b. Vendor and product names are simply Linux: Linux. No specific affected kernel versions are listed in the CNA data; the issue exists in any kernel build containing the unpatched pernet .pre_exit implementation.

The CVSS score of 5.5 indicates medium severity, and the EPSS score of less than 1% suggests a low but nonzero probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. An attacker would need to trigger the namespace exit sequence while another process holds the rtnl_mutex, which generally requires local privileged (root) access or the ability to create and delete network namespaces. The fix relies on a standard kernel update that removes the manual lock and uses the framework‑provided .exit_rtnl hook, eliminating the contention window.