{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98652 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98652 is a vulnerability in Linux, published on 18 Oct 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-98652 and fix it if it is affected.\n\nWhat it is: CVE-2026-98652 is a vulnerability in Linux, published on 18 Oct 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-98652 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-98652/ (Markdown: https://insights.sbomify.com/CVE-2026-98652/index.md)","id":"CVE-2026-98652","markdown":"https://insights.sbomify.com/CVE-2026-98652/index.md","name":"CVE-2026-98652","record":{"aliases":["AZL-108812","BELL-CVE-2026-98652","DEBIAN-CVE-2026-98652","GHSA-q542-rw7h-r852","UBUNTU-CVE-2026-98652"],"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":"low_privilege","summary":"A missing lock in the Linux kernel's KVM s390 module allows local attackers to trigger a race condition, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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: s390: Add missing srcu in kvm_s390_set_irq_state()\n\nLike kvm_s390_inject_vcpu(), kvm_s390_set_irq_state() also needs the\nkvm-\u003esrcu or the slots lock when performing the Store status operation.\n\nFix by taking kvm-\u003esrcu in kvm_s390_set_irq_state().","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: Add missing srcu in kvm_s390_set_irq_state()","id":"CVE-2026-98652","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 _gaccess_shadow_fault()","id":"CVE-2026-98653"},"packages":[],"prev":{"headline":"KVM: s390: Properly handle NULL pointer in dat_cond_set_storage_key()","id":"CVE-2026-98651"},"products":["Linux"],"published":"2026-10-18","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 missing lock in the Linux kernel's KVM s390 module allows local attackers to trigger a race condition, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-98652/"}