Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix fiemap wild read on empty truncated response smb3_fiemap() treats -E2BIG from SMB2_ioctl() as a truncated range blob and loops for the next chunk. If the server reports STATUS_BUFFER_OVERFLOW with OutputCount == 0, SMB2_ioctl() returns -E2BIG with out_data == NULL and out_data_len == 0, and the existing length checks accept the empty result. The loop then evaluates next = out_data[num - 1].file_offset + ... with num == 0, reading 16 bytes before NULL. Reject a truncated range blob that contains no range, so the resume offset is never computed from an empty response. Also require the last range in a truncated blob to advance the resume offset without overflowing, and to stay within the requested range; a malicious or broken server could otherwise make no progress or underflow len and loop forever. Free the previous response buffer before retrying. Reproduced on 6.6.87.2 with a malicious SMB2 server that answers FSCTL_QUERY_ALLOCATED_RANGES with STATUS_BUFFER_OVERFLOW and OutputCount == 0; an FS_IOC_FIEMAP ioctl on the mount oopses in cifs_fiemap() with CR2 = fffffffffffffff8. The code path is unchanged on mainline.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 to < 8e0d425b808c367f5033eb72aa4528ae18473627affected2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 to < 4a426ca5be7e3dedbe76575b967db04fbf01136faffected2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 to < 31f6dbb29fe17fa9595c7e8b19fd92915b03a4caaffected2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 to < f5baa17a0f316c235d61623ac8e8fb32c2b3c0ccaffected
Linux Linux
Default version status: affected
5.2affected0 to < 5.2unaffected6.12.117 to ≤ 6.12.*unaffected6.18.61 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected