{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89775 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89775 is a critical denial of service 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-89775 and fix it if it is affected.\n\nWhat it is: CVE-2026-89775 is a critical denial of service 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-89775 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-89775/ (Markdown: https://insights.sbomify.com/CVE-2026-89775/index.md)","id":"CVE-2026-89775","markdown":"https://insights.sbomify.com/CVE-2026-89775/index.md","name":"CVE-2026-89775","record":{"aliases":["BELL-CVE-2026-89775","DEBIAN-CVE-2026-89775","GHSA-4h2c-gw77-f478","UBUNTU-CVE-2026-89775"],"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 flaw in Linux kernel KVM arm64 TLB invalidation logic causes incorrect size calculations when the MMU is disabled, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: Handle negative S1 walk levels in VNCR TLB size evaluation\n\nComputing the effects of a TLB invalidation involves looking at\nthe size of the mapping cached by the TLB. For S1 mappings such as\nVNCR, this is deducted from the combination of the base granule size\nand the mapping level.\n\nHowever, this implies that the S1 MMU is *on*. When the MMU is off,\nwe indicate this with the level being set to a \"creative\" value of\n-127 (S1_MMU_DISABLED).\n\nThis ends-up being misinterpreted by pgshift_level_to_ttl() as it\ndoesn't handle negative levels at all (the level is immediately cast\nto a u8 and only the bottom two bits considered), leading to an\ninvalidation size of 0. Not helpful.\n\nTidy-up pgshift_level_to_ttl() to handle these negative levels, and\nttl_to_size() to always return SZ_1G when no valid TTL is present.\nThis allows the removal of open-coded checks for similar situations.\n\nNote that the check for a negative value not explicitely checking for\nS1_MMU_DISABLED is deliberate, so that actual negative levels introduced\nwith LVA2 and D128 can take the same path if we ever support them.","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: Handle negative S1 walk levels in VNCR TLB size evaluation","id":"CVE-2026-89775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"vxlan: vnifilter: enforce exact length of GROUP/GROUP6 attributes","id":"CVE-2026-89776"},"packages":[],"prev":{"headline":"Bluetooth: SCO: hold sk properly in sco_conn_ready","id":"CVE-2026-89774"},"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 flaw in Linux kernel KVM arm64 TLB invalidation logic causes incorrect size calculations when the MMU is disabled, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-89775/"}