{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98635 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98635 is a memory corruption 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-98635 and fix it if it is affected.\n\nWhat it is: CVE-2026-98635 is a memory corruption 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-98635 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-98635/ (Markdown: https://insights.sbomify.com/CVE-2026-98635/index.md)","id":"CVE-2026-98635","markdown":"https://insights.sbomify.com/CVE-2026-98635/index.md","name":"CVE-2026-98635","record":{"aliases":["DEBIAN-CVE-2026-98635","GHSA-xmm2-hmmq-mgf4","UBUNTU-CVE-2026-98635"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A malicious SCSI device can trigger an out-of-bounds write in the Linux kernel, potentially leading to code execution or system crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nscsi: block: Fix zones_cond out-of-bounds write on zone report\n\nblk_revalidate_disk_zones() sizes the zones_cond array from the disk\ncapacity and zone size, but the index used by blk_revalidate_zone_cond()\ncomes from the device-driven report_zones() walk and is never checked\nagainst the array size. A device reporting more zones than fit the array\nmakes blk_zone_set_cond() write out of bounds.\n\nOne way to reach this is a zone count exceeding 32 bits: both\nblk_revalidate_zone_args.nr_zones and struct zoned_disk_info.nr_zones are\nunsigned int, so a disk advertising more than UINT_MAX zones (e.g.  2^32 +\n1024 zones of one 512-byte logical block) gets its zone count truncated to\na small value, undersizing the array while the report walk keeps counting\nupward.\n\nCheck the index against the array size before storing the zone condition,\nand refuse to revalidate when the zone count does not fit 32 bits.","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":"scsi: block: Fix zones_cond out-of-bounds write on zone report","id":"CVE-2026-98635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"squashfs: Add dictionary size range check to prevent shift-out-of-bounds","id":"CVE-2026-98636"},"packages":[],"prev":{"headline":"scsi: sd_zbc: Reject disks with too many zones","id":"CVE-2026-98634"},"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 malicious SCSI device can trigger an out-of-bounds write in the Linux kernel, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-98635/"}