{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89915 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89915 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-89915 and fix it if it is affected.\n\nWhat it is: CVE-2026-89915 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-89915 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-89915/ (Markdown: https://insights.sbomify.com/CVE-2026-89915/index.md)","id":"CVE-2026-89915","markdown":"https://insights.sbomify.com/CVE-2026-89915/index.md","name":"CVE-2026-89915","record":{"aliases":["BELL-CVE-2026-89915","DEBIAN-CVE-2026-89915","GHSA-crqv-c33h-f779","UBUNTU-CVE-2026-89915"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"none","summary":"A race condition in KVM arm64 TLB invalidation logic can cause missed invalidations, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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: Remove VM-wide VNCR mapping counter\n\nThe global VNCR mapping counter is used to decide whether an L1\nprovided VNCR page is mapped in L0 on any CPU at the point of\ndealing with a TLB invalidation. It is incremented when a mapping\nis made in the fixmap, and decremented when unmapped.\n\nAs it turns out, this tracking has several flaws:\n\n- we are trying to invalidate TLBs, and the mapping is only an\n  opportunistic consequence of the TLB. Checking this counter to\n  decide whether a TLB needs to be invalidated may result in missed\n  invalidations.\n\n- an L1 vcpu invalidating its own TLB (a very likely case) will not\n  succeed in invalidating the VNCR pseudo TLB because that page is\n  not mapped in L0 at this stage.\n\nGiven that this tracking fails at delivering the minimum guarantees\nthat are required and is only a performance optimisation, remove it\ncompletely.","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: Remove VM-wide VNCR mapping counter","id":"CVE-2026-89915","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":"KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry","id":"CVE-2026-89916"},"packages":[],"prev":{"headline":"KVM: arm64: Sign-extend VA for range-based TLBI invalidation","id":"CVE-2026-89914"},"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 race condition in KVM arm64 TLB invalidation logic can cause missed invalidations, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-89915/"}