The vulnerability involves the Linux kernel's VFS layer where disconnected dentries created during open_by_handle_at() calls may not be correctly marked as disconnected if lookup_one_unlocked() fails during reconnect_path(). Following a prior commit that changed how disconnected dentries are tracked, this inconsistency causes some dentries to be leaked in memory rather than reclaimed promptly. If an unmount occurs before memory reclaim, it triggers the "Busy inodes after unmount" bug. The fix ensures all dentries created under a disconnected parent are also marked as disconnected to prevent leaks.

This vulnerability can lead to memory leaks of dentries in the kernel, causing resource exhaustion and system instability. The "Busy inodes after unmount" condition may prevent successful unmount operations, potentially impacting system reliability and availability. Confidentiality, integrity, and availability impacts are rated high per the CVSS vector, reflecting the potential for significant disruption.

A fix has been implemented in the Linux kernel to address this issue by ensuring all dentries under a disconnected parent are marked as disconnected. Users should apply the official kernel updates that include this patch to remediate the vulnerability. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended mitigation. Patch status is not explicitly provided here; users should consult the official Linux kernel advisories or distribution security updates for the exact fixed versions and apply them accordingly.