summaryrefslogtreecommitdiff
path: root/scripts/bash-completion
diff options
context:
space:
mode:
authorVitaly Grigoryev <Vitaly.Grigoryev@kaspersky.com>2025-08-25 13:08:55 +0300
committerKonstantin Komarov <almaz.alexandrovich@paragon-software.com>2025-09-10 11:01:39 +0200
commit736fc7bf5f68f6b74a0925b7e072c571838657d2 (patch)
tree4b2c2d9ad679b9a8fbd9d4962d585733b158d0b7 /scripts/bash-completion
parent4e8011ffec79717e5fdac43a7e79faf811a384b7 (diff)
fs: ntfs3: Fix integer overflow in run_unpack()
The MFT record relative to the file being opened contains its runlist, an array containing information about the file's location on the physical disk. Analysis of all Call Stack paths showed that the values of the runlist array, from which LCNs are calculated, are not validated before run_unpack function. The run_unpack function decodes the compressed runlist data format from MFT attributes (for example, $DATA), converting them into a runs_tree structure, which describes the mapping of virtual clusters (VCN) to logical clusters (LCN). The NTFS3 subsystem also has a shortcut for deleting files from MFT records - in this case, the RUN_DEALLOCATE command is sent to the run_unpack input, and the function logic provides that all data transferred to the runlist about file or directory is deleted without creating a runs_tree structure. Substituting the runlist in the $DATA attribute of the MFT record for an arbitrary file can lead either to access to arbitrary data on the disk bypassing access checks to them (since the inode access check occurs above) or to destruction of arbitrary data on the disk. Add overflow check for addition operation. Found by Linux Verification Center (linuxtesting.org) with SVACE. Fixes: 4342306f0f0d ("fs/ntfs3: Add file operations and implementation") Signed-off-by: Vitaly Grigoryev <Vitaly.Grigoryev@kaspersky.com> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Diffstat (limited to 'scripts/bash-completion')
0 files changed, 0 insertions, 0 deletions