CVE-2026-98684

smb: client: flush and commit data before querying allocated ranges

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: flush and commit data before querying allocated ranges The mode 0 / FALLOC_FL_KEEP_SIZE fallocate emulation for small interior ranges in smb3_simple_fallocate_range() issues FSCTL_QUERY_ALLOCATED_RANGES and zero-fills any sub-range the server reports as an unallocated hole, to force block allocation without changing file contents. This is unsafe against Windows servers. Per the Win32 documentation, FSCTL_QUERY_ALLOCATED_RANGES only reports ranges that *may* contain nonzero data and is explicitly not coherent with recently written data: "a call to FSCTL_QUERY_ALLOCATED_RANGES [after writing to a network file] would not necessarily return a correct list of allocated regions. To ensure coherency [...] flush the data to the file" fsx (generic/363) reproduces the resulting corruption against Windows Server 2022: a range is written, an uncached read returns the data, yet the next FSCTL_QUERY_ALLOCATED_RANGES on that range reports it as a whole hole, so the emulation overwrites live data with zeroes. A network trace confirmed the WRITE, the READ returning data and the query returning an empty range list within microseconds. Samba does not exhibit this; its query is coherent with the written data. Write back the dirty pages, drain any outstanding I/O and issue an SMB2 FLUSH to force the server to commit the data before querying the allocated ranges, so the query reflects the data actually present. With this, generic/363 passes against both Windows Server 2022 and Samba over 100000 fsx operations.

Key facts

Published
18 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.215% of CVEs (scores for 18 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
  • 966a3cb7c7db786452a87afdc3b48858fc4d4d6b up to but excluding 6787575545cd8af1da3778d7c1ae43a4398a6b26 (affected)
  • 966a3cb7c7db786452a87afdc3b48858fc4d4d6b up to but excluding f82242fe3109a3ef72f429540b5bdde08fbfb0e4 (affected)
  • 966a3cb7c7db786452a87afdc3b48858fc4d4d6b up to but excluding bf84e44ff0ed802778eafd7ecb623635379cb506 (affected)
  • 966a3cb7c7db786452a87afdc3b48858fc4d4d6b up to but excluding aa994489bd835547c191827acc460192e147032d (affected)
  • c406bb9ece6ef63721daab106f132ff4b4234e81 (affected)
  • 2f9f4a2d0e6fcf0673ed51195e06e47abe966900 (affected)
  • 5e397c943424de94879830e72c95f2679e297a76 (affected)
  • 5.10.50 up to but excluding 5.11 (affected)
  • 5.12.17 up to but excluding 5.13 (affected)
  • 5.13.2 up to but excluding 5.14 (affected)
LinuxLinux
  • Default status: affected
  • 5.14 (affected)
  • 0 up to but excluding 5.14 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References