{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98683 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98683 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98683 and fix it if it is affected.\n\nWhat it is: CVE-2026-98683 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98683 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98683/ (Markdown: https://insights.sbomify.com/CVE-2026-98683/index.md)","id":"CVE-2026-98683","markdown":"https://insights.sbomify.com/CVE-2026-98683/index.md","name":"CVE-2026-98683","record":{"aliases":["BELL-CVE-2026-98683","DEBIAN-CVE-2026-98683","GHSA-f8wg-49h3-2qvh","UBUNTU-CVE-2026-98683"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel SMB client","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel SMB client allows attackers to read stale data from zeroed file ranges due to missing dirty page flushes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"smb: client: flush dirty data before zeroing a range","id":"CVE-2026-98683","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"smb: client: flush and commit data before querying allocated ranges","id":"CVE-2026-98684"},"packages":[],"prev":{"headline":"smb: client: drain and invalidate before server-side copy/clone","id":"CVE-2026-98682"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel SMB client allows attackers to read stale data from zeroed file ranges due to missing dirty page flushes.","url":"https://insights.sbomify.com/CVE-2026-98683/"}