{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89919 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89919 is a high-severity 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-89919 and fix it if it is affected.\n\nWhat it is: CVE-2026-89919 is a high-severity 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-89919 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-89919/ (Markdown: https://insights.sbomify.com/CVE-2026-89919/index.md)","id":"CVE-2026-89919","markdown":"https://insights.sbomify.com/CVE-2026-89919/index.md","name":"CVE-2026-89919","record":{"aliases":["DEBIAN-CVE-2026-89919","GHSA-xrcv-f2mv-23j2","UBUNTU-CVE-2026-89919"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"low_privilege","summary":"A race condition in KVM s390 keyop allows concurrent access to stale memory mappings, potentially leading to memory corruption and privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"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:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: keyop: use mmu_lock to read gmap-\u003easce\n\nEvery other dat_* consumer in this file (kvm_s390_get_skeys,\nset_skeys, get_cmma_bits, set_cmma_bits, MEM_CLR_CMMA,\nkvm_s390_fixup_prefix, kvm_test_age_gfn, kvm_age_gfn) reads\nkvm-\u003earch.gmap-\u003easce *inside* the mmu_lock read-side. keyop is the only\noutlier.\n\ngmap-\u003easce is mutated under write_lock(mmu_lock) by gmap_set_limit()\nand keyop might use a stale asce value for walking as KVM_S390_KEYOP\nand KVM_S390_VM_MEM_LIMIT_SIZE can run concurrently. This can result\nin memory corruption.","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: s390: keyop: use mmu_lock to read gmap-\u003easce","id":"CVE-2026-89919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"KVM: s390: Fix memory corruption by not reinjecting CK machine checks","id":"CVE-2026-89920"},"packages":[],"prev":{"headline":"KVM: arm64: Correctly handle end of VA space TLBI invalidation","id":"CVE-2026-89918"},"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 s390 keyop allows concurrent access to stale memory mappings, potentially leading to memory corruption and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89919/"}