cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 04b38d601239b4d9be641b412cf4b7456a041c67 · < c2a0dcb5a7a1516aa6eb6d5cedca6a8e76527028| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0
With len == 0 (clone to EOF), the effective length is computed as:
len = src_inode->i_size - off;
If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range(). The existing off >= i_size check fires only after the ioctl has already been sent.
Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk. Reject off > src_size with -EINVAL. Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().
From the CVE record · Linux
The Linux kernel’s CIFS file-remapping function can calculate a negative length when a clone-to-EOF request uses an offset beyond the source file’s size. This corrupts the ByteCount in a duplicate-extents request and inverts a file writeback range; the input does not specify attacker access requirements.
Engineers running Linux kernels with CIFS support should check their versions; affected versions are not specified.