{"api_version":"1","generated_at":"2026-10-22T17:45:18+00:00","cve":"CVE-2026-98683","urls":{"html":"https://cve.report/CVE-2026-98683","api":"https://cve.report/api/cve/CVE-2026-98683.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98683","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98683"},"summary":{"title":"smb: client: flush dirty data before zeroing a range","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: flush dirty data before zeroing a range\n\nsmb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the\npage cache over the target range with truncate_pagecache_range() and\nthen issuing FSCTL_SET_ZERO_DATA to the server.\n\nDirty data was only flushed conditionally, when the range reached or\nextended EOF.  For a purely interior zero range that does not reach\nEOF, no flush happened, so a dirty folio overlapping the range could\nbe written back to the server after the FSCTL and refill the range\nthat was just zeroed with stale data.\n\nFix this by unconditionally flushing and waiting for dirty data in the\nrange before invalidating the page cache and issuing\nFSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in\ncommit d7d2adcd022b (\"smb/client: flush dirty data before punching a\nhole\"); the two paths are structurally identical here.\n\nThis is observed as generic/363 randomly reading stale data where a\nzeroed range is expected against Windows Server.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:21","updated_at":"2026-10-19 10:19:32"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb","name":"https://git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c","name":"https://git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862","name":"https://git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98683","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98683","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 cecf4114069fc19629d284710fd783d56bbca862 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 e8ba21c7e6ef3d4cb617858760673877b2e4a2bb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 91d1dfae464987aaf6c79ff51d8674880fb3be77 8f8d32c1044f70e46e87550e039a15ff20a4b21c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 13af7446428771e9e529284d390e7994df8be683 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0a9423f99ded38b32bd1864347332cc557e6b141 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7dfa4279c55f467a88e653a5d544817181b22aea git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.1.110 6.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6.51 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10.10 6.11 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.11","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.11 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.56 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.10 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/smb/client/smb2ops.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"cecf4114069fc19629d284710fd783d56bbca862","status":"affected","version":"91d1dfae464987aaf6c79ff51d8674880fb3be77","versionType":"git"},{"lessThan":"e8ba21c7e6ef3d4cb617858760673877b2e4a2bb","status":"affected","version":"91d1dfae464987aaf6c79ff51d8674880fb3be77","versionType":"git"},{"lessThan":"8f8d32c1044f70e46e87550e039a15ff20a4b21c","status":"affected","version":"91d1dfae464987aaf6c79ff51d8674880fb3be77","versionType":"git"},{"status":"affected","version":"13af7446428771e9e529284d390e7994df8be683","versionType":"git"},{"status":"affected","version":"0a9423f99ded38b32bd1864347332cc557e6b141","versionType":"git"},{"status":"affected","version":"7dfa4279c55f467a88e653a5d544817181b22aea","versionType":"git"},{"lessThan":"6.2","status":"affected","version":"6.1.110","versionType":"semver"},{"lessThan":"6.7","status":"affected","version":"6.6.51","versionType":"semver"},{"lessThan":"6.11","status":"affected","version":"6.10.10","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/smb/client/smb2ops.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.11"},{"lessThan":"6.11","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.56","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.56","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.10","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1.110","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6.51","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: flush dirty data before zeroing a range\n\nsmb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the\npage cache over the target range with truncate_pagecache_range() and\nthen issuing FSCTL_SET_ZERO_DATA to the server.\n\nDirty data was only flushed conditionally, when the range reached or\nextended EOF.  For a purely interior zero range that does not reach\nEOF, no flush happened, so a dirty folio overlapping the range could\nbe written back to the server after the FSCTL and refill the range\nthat was just zeroed with stale data.\n\nFix this by unconditionally flushing and waiting for dirty data in the\nrange before invalidating the page cache and issuing\nFSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in\ncommit d7d2adcd022b (\"smb/client: flush dirty data before punching a\nhole\"); the two paths are structurally identical here.\n\nThis is observed as generic/363 randomly reading stale data where a\nzeroed range is expected against Windows Server."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:23:53.516Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862"},{"url":"https://git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb"},{"url":"https://git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c"}],"title":"smb: client: flush dirty data before zeroing a range","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98683","datePublished":"2026-10-18T15:45:50.014Z","dateReserved":"2026-09-25T10:25:14.364Z","dateUpdated":"2026-10-19T09:23:53.516Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:21","lastModifiedDate":"2026-10-19 10:19:32","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98683","Ordinal":"1","Title":"smb: client: flush dirty data before zeroing a range","CVE":"CVE-2026-98683","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98683","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: flush dirty data before zeroing a range\n\nsmb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the\npage cache over the target range with truncate_pagecache_range() and\nthen issuing FSCTL_SET_ZERO_DATA to the server.\n\nDirty data was only flushed conditionally, when the range reached or\nextended EOF.  For a purely interior zero range that does not reach\nEOF, no flush happened, so a dirty folio overlapping the range could\nbe written back to the server after the FSCTL and refill the range\nthat was just zeroed with stale data.\n\nFix this by unconditionally flushing and waiting for dirty data in the\nrange before invalidating the page cache and issuing\nFSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in\ncommit d7d2adcd022b (\"smb/client: flush dirty data before punching a\nhole\"); the two paths are structurally identical here.\n\nThis is observed as generic/363 randomly reading stale data where a\nzeroed range is expected against Windows Server.","Type":"Description","Title":"smb: client: flush dirty data before zeroing a range"}]}}}