{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90176 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90176 is a high-severity vulnerability in Linux, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90176 and fix it if it is affected.\n\nWhat it is: CVE-2026-90176 is a high-severity vulnerability in Linux, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90176 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-90176/ (Markdown: https://insights.sbomify.com/CVE-2026-90176/index.md)","id":"CVE-2026-90176","markdown":"https://insights.sbomify.com/CVE-2026-90176/index.md","name":"CVE-2026-90176","record":{"aliases":["AZL-102714","BELL-CVE-2026-90176","DEBIAN-CVE-2026-90176","GHSA-rxgv-prwv-26g4","UBUNTU-CVE-2026-90176"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel ksmbd","requires_auth":"low_privilege","summary":"Attackers can bypass byte-range locks in ksmbd to perform unauthorized reads or writes on single-byte file ranges.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Do not skip lock checks for single-byte ranges\n\ncheck_lock_range() uses inclusive ranges. Its callers pass the end\noffset as start + length - 1, so start == end represents a valid\nsingle-byte range rather than an empty range.\n\nThe start == end shortcut therefore skips mandatory byte-range lock\nchecks for one-byte reads, writes, copychunk operations and one-byte\ntruncate ranges. A conflicting lock covering that byte is not checked\nand the operation is allowed to proceed.\n\nRemove the shortcut. The truncate size == inode-\u003ei_size case is already\nhandled by only calling check_lock_range() when the new size differs\nfrom the current file size.","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":"ksmbd: Do not skip lock checks for single-byte ranges","id":"CVE-2026-90176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"bpf: Check pointer type for all atomic RMW paths","id":"CVE-2026-90177"},"packages":[],"prev":{"headline":"smb: server: fix leak of ksmbd_ipc_login_request_ext() returned buffer","id":"CVE-2026-90175"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Attackers can bypass byte-range locks in ksmbd to perform unauthorized reads or writes on single-byte file ranges.","url":"https://insights.sbomify.com/CVE-2026-90176/"}