In the Linux kernel, the order in which the mrec_lock mutexes are acquired for NTFS inodes can produce a deadlock. The bug allows ntfs_file_fsync, ntfs_dir_fsync, or __ntfs_write_inode to hold the mrec_lock of a target inode while ntfs_rename simultaneously holds the mrec_lock of a parent directory, causing a mutual wait. The result is a hung process and a temporary denial of service for operations that involve file renaming or synchronization on NTFS filesystems. The vulnerability does not disclose code execution or data exfiltration; its impact is confined to service availability.

All Linux kernel releases that include the NTFS filesystem code before the patch described in the advisory are affected. The advisory does not specify particular kernel versions, so any kernel that has not received the fix could potentially be vulnerable.

Based on the description, the vulnerability is only exploitable when the attacker can trigger the problematic lock sequence on a system that mounts an NTFS filesystem. It is inferred that an attacker with local root privileges could deliberately invoke rename or fsync operations that lead to the deadlock, or a process running with elevated rights could passively cause it through concurrent filesystem activity. The EPSS score is <1%, indicating a very low probability of exploitation, and the CVSS score is 5.5, indicating moderate severity. The flaw is not listed in CISA's KEV catalog, indicating that publicly known exploit cases have not been reported. However, the severity of a system halt or significant slowdown makes this a notable availability risk that should be mitigated promptly.