CVE-2026-98684

published 18 Oct 2026 · updated 17 Nov 2026

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

2.5LowCVSS 2.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f82242fe3109a3ef72f429540b5bdde08fbfb0e4, Kernel 5.11, Kernel 5.13 and 7 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <f82242fe3109a3ef72f429540b5bdde08fbfb0e4, >=5.10.50 <5.11, >=5.12.17 <5.13, >=5.13.2 <5.14, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <6787575545cd8af1da3778d7c1ae43a4398a6b26, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <aa994489bd835547c191827acc460192e147032d, >=966a3cb7c7db786452a87afdc3b48858fc4d4d6b <bf84e44ff0ed802778eafd7ecb623635379cb506, =2f9f4a2d0e6fcf0673ed51195e06e47abe966900, =5.14, =5e397c943424de94879830e72c95f2679e297a76, =c406bb9ece6ef63721daab106f132ff4b4234e81f82242fe3109a3ef72f429540b5bdde08fbfb0e4, 5.11, 5.13, 5.14, 6787575545cd8af1da3778d7c1ae43a4398a6b26, aa994489bd835547c191827acc460192e147032d, bf84e44ff0ed802778eafd7ecb623635379cb506
linux-kernel: Kernel>=5.12.17 <5.13, >=5.13.2 <5.14, >=5.14.0 <6.12.117, >=6.13.0 <6.18.56, >=6.19.0 <7.2.10, >=5.10.50 <5.115.13, 5.14, 6.12.117, 6.18.56, 7.2.10, 5.11

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98684 severity on Zeptric[![CVE-2026-98684](https://zeptric.io/badge/cve/CVE-2026-98684.svg)](https://zeptric.io/cve/CVE-2026-98684)