https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 07:27:26 +0000 https://vulnerability.circl.lu/vuln/cve-2026-72190 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: fix mrec_lock ABBA deadlock in rename</p> <p>ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode&#39;s mrec_lock before taking the mrec_lock of its parent directory.</p> <p>ntfs_rename() takes old_ni-&gt;mrec_lock and old_dir_ni-&gt;mrec_lock before taking new_ni-&gt;mrec_lock for an existing target, or new_dir_ni-&gt;mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target.</p> <p>Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: fix mrec_lock ABBA deadlock in rename</p> <p>ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode&#39;s mrec_lock before taking the mrec_lock of its parent directory.</p> <p>ntfs_rename() takes old_ni-&gt;mrec_lock and old_dir_ni-&gt;mrec_lock before taking new_ni-&gt;mrec_lock for an existing target, or new_dir_ni-&gt;mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target.</p> <p>Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().</p> https://vulnerability.circl.lu/vuln/cve-2026-72190