CVE-2026-98684: Linux
EPSS: 0.2% probability of exploitation activity in the next 30 days.
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.
What to do
The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.
- Linux, from 5.10.50, before 5.11: fixed in 5.11
- Linux, from 5.12.17, before 5.13: fixed in 5.13
- Linux, from 5.13.2, before 5.14: fixed in 5.14
- Linux, from 5.14, before 6.12.117: fixed in 6.12.117
- Linux, from 6.13, before 6.18.56: fixed in 6.18.56
- Linux, from 6.19, before 7.2.10: fixed in 7.2.10
Affected products
- Linux Linux: from 5.10.50, before 5.11 (fixed in 5.11); from 5.12.17, before 5.13 (fixed in 5.13); from 5.13.2, before 5.14 (fixed in 5.14); from 5.14, before 6.12.117 (fixed in 6.12.117); from 6.13, before 6.18.56 (fixed in 6.18.56); from 6.19, before 7.2.10 (fixed in 7.2.10)
Published 2026-10-18. Last modified 2026-11-10.