{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89918 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89918 is a critical vulnerability in Linux, published on 16 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-89918 and fix it if it is affected.\n\nWhat it is: CVE-2026-89918 is a critical vulnerability in Linux, published on 16 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-89918 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-89918/ (Markdown: https://insights.sbomify.com/CVE-2026-89918/index.md)","id":"CVE-2026-89918","markdown":"https://insights.sbomify.com/CVE-2026-89918/index.md","name":"CVE-2026-89918","record":{"aliases":["BELL-CVE-2026-89918","DEBIAN-CVE-2026-89918","GHSA-hcq6-hvjh-vf66","UBUNTU-CVE-2026-89918"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"none","summary":"A logic error in KVM arm64 TLB invalidation causes failed invalidations at the end of the VA space, potentially allowing stale TLB entries to persist.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/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\nKVM: arm64: Correctly handle end of VA space TLBI invalidation\n\nOur TLB invalidation by VA code is based on comparing two ranges,\none defined by the TLB, and one defined by the TLBI instruction.\n\nEach range is defined by a start and a size. However, the way the\ncomparison is done doesn't account for address rollover, as it\ncompares an address with (base + size). This works nicely until\nthis expression represent the last page/block in the TTBR1 VA space,\nas the result is a big fat 0. And a failed TLB invalidation.\n\nRewrite the comparison in a way that is immune to the address\nrollover (making the end address inclusive instead of exclusive),\nand move this into a common helper that is used by both VA and IPA\ninvalidations, as suggested by Hyunwoo Kim (although the IPA version\ndidn't suffer from this particular problem, obviously).","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":"KVM: arm64: Correctly handle end of VA space TLBI invalidation","id":"CVE-2026-89918","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"KVM: s390: keyop: use mmu_lock to read gmap-\u003easce","id":"CVE-2026-89919"},"packages":[],"prev":{"headline":"KVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping","id":"CVE-2026-89917"},"products":["Linux"],"published":"2026-09-16","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 logic error in KVM arm64 TLB invalidation causes failed invalidations at the end of the VA space, potentially allowing stale TLB entries to persist.","url":"https://insights.sbomify.com/CVE-2026-89918/"}