fs/ntfs3: fix mount failure for sparse runs in run_unpack()

commit 801f614ba263cb37624982b27b4c82f3c3c597a9 upstream.

Some NTFS volumes failed to mount because sparse data runs were not
handled correctly during runlist unpacking. The code performed arithmetic
on the special SPARSE_LCN64 marker, leading to invalid LCN values and
mount errors.

Add an explicit check for the case described above, marking the run as
sparse without applying arithmetic.

Fixes: 736fc7bf5f68 ("fs: ntfs3: Fix integer overflow in run_unpack()")
Cc: stable@vger.kernel.org
Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Konstantin Komarov
2025-09-18 13:35:24 +03:00
committed by Greg Kroah-Hartman
parent 7ad2c3ae07
commit 5fd1a6c631

View File

@@ -984,8 +984,12 @@ int run_unpack(struct runs_tree *run, struct ntfs_sb_info *sbi, CLST ino,
if (!dlcn)
return -EINVAL;
if (check_add_overflow(prev_lcn, dlcn, &lcn))
/* Check special combination: 0 + SPARSE_LCN64. */
if (!prev_lcn && dlcn == SPARSE_LCN64) {
lcn = SPARSE_LCN64;
} else if (check_add_overflow(prev_lcn, dlcn, &lcn)) {
return -EINVAL;
}
prev_lcn = lcn;
} else
return -EINVAL;