CVE Catalog

CVE-2026-98684

Low risk· EPSS 5%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.17%

5th percentile - higher than 5% of all known CVEs

Summary

In the Linux kernel SMB client, the fallocate emulation for small interior ranges (mode 0 / FALLOC_FL_KEEP_SIZE) issued FSCTL_QUERY_ALLOCATED_RANGES without first flushing data. Contrary to Win32 documentation, this query is not coherent with recently written data, so the server could report a written range as unallocated and the emulation overwrote live data with zeroes. The issue affects Windows servers; Samba does not exhibit this behavior.

Risk Assessment

On systems mounting SMB shares from Windows servers, silent data corruption may occur — written data is overwritten with zeroes during fallocate operations. This leads to file loss or corruption without warning.

Recommendation

Update the Linux kernel to a version containing the fix that writes back dirty pages, drains outstanding I/O and issues an SMB2 FLUSH before querying allocated ranges. Until patched, avoid fallocate operations with mode 0 / FALLOC_FL_KEEP_SIZE on SMB shares hosted on Windows servers.

Other vulnerabilities in Linux kernel SMB client

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS