{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89727 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89727 is a denial of service vulnerability in Linux, published on 11 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-89727 and fix it if it is affected.\n\nWhat it is: CVE-2026-89727 is a denial of service vulnerability in Linux, published on 11 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-89727 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-89727/ (Markdown: https://insights.sbomify.com/CVE-2026-89727/index.md)","id":"CVE-2026-89727","markdown":"https://insights.sbomify.com/CVE-2026-89727/index.md","name":"CVE-2026-89727","record":{"aliases":["DEBIAN-CVE-2026-89727","GHSA-v32g-7j7h-69wx","UBUNTU-CVE-2026-89727"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel KVM","requires_auth":"low_privilege","summary":"A malicious guest can trigger a kernel panic on the host by writing an invalid interrupt ID, causing denial of service if panic_on_warn is enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nKVM: arm64: GICv2: Don't WARN on out-of-range GICV_DIR INTID\n\nvgic_v2_deactivate() passes the INTID a guest wrote to GICV_DIR straight\nto vgic_get_vcpu_irq(), and treats a failed lookup as a \"can't happen\"\ncondition with WARN_ON_ONCE().\n\nThe guest can make it happen at will, though: for any INTID outside of\nthe implemented SGI, PPI and SPI ranges the lookup returns NULL, since\nGICv2 has no LPIs. A guest running with EOImode==1 writing such an INTID\nto GICV_DIR triggers the WARN, and panics hosts running with\npanic_on_warn.\n\nDrop the WARN and ignore failed lookups.","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: GICv2: Don't WARN on out-of-range GICV_DIR INTID","id":"CVE-2026-89727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"i3c: renesas: Fix out-of-bounds access for newdevs mask","id":"CVE-2026-89728"},"packages":[],"prev":{"headline":"lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen()","id":"CVE-2026-89726"},"products":["Linux"],"published":"2026-09-11","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 guest can trigger a kernel panic on the host by writing an invalid interrupt ID, causing denial of service if panic_on_warn is enabled.","url":"https://insights.sbomify.com/CVE-2026-89727/"}