- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 966a3cb7c7db786452a87afdc3b48858fc4d4d6b – < 6787575545cd8af1da3778d7c1ae43a4398a6b26
- affected 966a3cb7c7db786452a87afdc3b48858fc4d4d6b – < f82242fe3109a3ef72f429540b5bdde08fbfb0e4
- affected 966a3cb7c7db786452a87afdc3b48858fc4d4d6b – < bf84e44ff0ed802778eafd7ecb623635379cb506
- affected 966a3cb7c7db786452a87afdc3b48858fc4d4d6b – < aa994489bd835547c191827acc460192e147032d
- affected c406bb9ece6ef63721daab106f132ff4b4234e81
- affected 2f9f4a2d0e6fcf0673ed51195e06e47abe966900
- affected 5e397c943424de94879830e72c95f2679e297a76
- affected 5.10.50 – < 5.11
- affected 5.12.17 – < 5.13
- affected 5.13.2 – < 5.14
- affected 5.14
- unaffected < 5.14
- unaffected 6.12.117 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/6787575545cd8af1da3778d7c1ae43a4398a6b26 (opens in a new tab)
- https://git.kernel.org/stable/c/f82242fe3109a3ef72f429540b5bdde08fbfb0e4 (opens in a new tab)
- https://git.kernel.org/stable/c/bf84e44ff0ed802778eafd7ecb623635379cb506 (opens in a new tab)
- https://git.kernel.org/stable/c/aa994489bd835547c191827acc460192e147032d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103938 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98684)Record last updated .