A lock inversion deadlock in the Linux kernel’s NTFS‑3.0 module occurs when ntfs_read_folio() holds the inode mutex (ni_lock) while another task holds a page lock needed for the same read. The inverted lock order allows two concurrently executing reads to block each other, causing a hung kernel thread and system unresponsiveness. The flaw is identified by CWE‑667 (Race Condition) and CWE‑833 (Incorrect Block Ordering).

All Linux kernel releases containing the ntfs3 driver before the commits cfe246b3181 and e37a75bb866c are vulnerable, as the problem exists in the ntfs_read_folio and ni_read_folio_cmpr code paths. The exact kernel version ranges are not listed, so any kernel that has not yet incorporated this patch may be affected.

The CVSS score of 5.5 reflects a moderate impact, but exploitation requires local access to a system with an NTFS‑3.0 mount that can trigger concurrent read activity – for example, background indexing or readahead. In this scenario an adversary could repeatedly provoke the deadlock, resulting in a denial‑of‑service condition. The EPSS score of less than 1% indicates a very low probability of exploitation in the wild, and the vulnerability is not in the CISA KEV catalog. Nevertheless, the potential for kernel hangs means that environments with intensive NTFS usage merit prompt mitigation.