{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97991 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97991 is a high-severity memory corruption vulnerability in Linux, published on 25 Sep 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-97991 and fix it if it is affected.\n\nWhat it is: CVE-2026-97991 is a high-severity memory corruption vulnerability in Linux, published on 25 Sep 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-97991 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-97991/ (Markdown: https://insights.sbomify.com/CVE-2026-97991/index.md)","id":"CVE-2026-97991","markdown":"https://insights.sbomify.com/CVE-2026-97991/index.md","name":"CVE-2026-97991","record":{"aliases":["AZL-104381","BELL-CVE-2026-97991","DEBIAN-CVE-2026-97991","GHSA-hprw-93rc-4v5g","UBUNTU-CVE-2026-97991"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A guest VM can trigger out-of-bounds reads and writes in the Linux kernel's vdpa_sim_blk driver, potentially leading to code execution or data exposure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvdpa_sim_blk: reject out-of-range sector starts\n\nvdpasim_blk_check_range() logs an invalid start sector but continues\nvalidating the request.  The subsequent unsigned capacity subtraction can\nunderflow and let an out-of-range buffer offset reach the data path.\n\nThe invalid offset is used by three request paths.  VIRTIO_BLK_T_OUT\ncopies guest data to blk-\u003ebuffer + offset through\nvringh_iov_pull_iotlb(), causing an out-of-bounds write in\n_copy_from_iter() or memcpy().  VIRTIO_BLK_T_IN copies from\nblk-\u003ebuffer + offset to the guest through vringh_iov_push_iotlb(),\ncausing an out-of-bounds read in _copy_to_iter().\nVIRTIO_BLK_T_WRITE_ZEROES passes blk-\u003ebuffer + offset to memset(),\ncausing an out-of-bounds write.\n\nReject starts at or beyond the capacity before the subtraction.  Treat the\ncapacity boundary as invalid because the IN and OUT paths round byte counts\ndown to sectors for validation but later copy the original byte counts.  A\nsub-sector request at the capacity boundary would otherwise still access\npast the end of the buffer.\n\nI found this bug myself, though the patch was written with AI assistance.","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":"vdpa_sim_blk: reject out-of-range sector starts","id":"CVE-2026-97991","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"vhost-vdpa: protect config_ctx from being freed under the config callback","id":"CVE-2026-97992"},"packages":[],"prev":{"headline":"vdpa_sim_net: check TX pull result before RX copy","id":"CVE-2026-97990"},"products":["Linux"],"published":"2026-09-25","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":"A guest VM can trigger out-of-bounds reads and writes in the Linux kernel's vdpa_sim_blk driver, potentially leading to code execution or data exposure.","url":"https://insights.sbomify.com/CVE-2026-97991/"}