CVE-2026-99274

smb: client: fix fiemap wild read on empty truncated response

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.

Key facts

Published
7 Nov 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.157% likely to be exploited in the next 30 days, higher than 4.886% of CVEs (scores for 15 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 up to but excluding 8e0d425b808c367f5033eb72aa4528ae18473627 (affected)
  • 2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 up to but excluding 4a426ca5be7e3dedbe76575b967db04fbf01136f (affected)
  • 2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 up to but excluding 31f6dbb29fe17fa9595c7e8b19fd92915b03a4ca (affected)
  • 2f3ebaba13cebd8badfb9aed31c0cf3cc82eb4f4 up to but excluding f5baa17a0f316c235d61623ac8e8fb32c2b3c0cc (affected)
LinuxLinux
  • Default status: affected
  • 5.2 (affected)
  • 0 up to but excluding 5.2 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.61 up to and including 6.18.* (unaffected)
  • 7.3.2 up to and including 7.3.* (unaffected)
  • 7.4-rc1 up to and including * (unaffected)

Timeline

  1. 7 Nov 2026 Published

References