{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98470 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98470 is a denial of service 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-98470 and fix it if it is affected.\n\nWhat it is: CVE-2026-98470 is a denial of service 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-98470 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-98470/ (Markdown: https://insights.sbomify.com/CVE-2026-98470/index.md)","id":"CVE-2026-98470","markdown":"https://insights.sbomify.com/CVE-2026-98470/index.md","name":"CVE-2026-98470","record":{"aliases":["DEBIAN-CVE-2026-98470","GHSA-j632-93gc-r86q","UBUNTU-CVE-2026-98470"],"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 local attacker can crash a protected KVM host by triggering a kernel warning via an unknown ioctl, causing a panic 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: Don't WARN on an unknown VM ioctl in protected mode\n\nkvm_pkvm_ioctl_allowed() WARNs when kvm_get_cap_for_kvm_ioctl() doesn't\nfind the ioctl number in vm_ioctl_caps[], and kvm_arch_vm_ioctl() calls\nit for every number the generic code doesn't handle, so\nioctl(vm_fd, 0xdeadbeef) from userspace taints a pKVM host and panics it\nunder panic_on_warn. The lookup is fed userspace input: return false,\nand userspace gets the -EINVAL kvm_arch_vm_ioctl() returns for that\nnumber on a host without pKVM.","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: Don't WARN on an unknown VM ioctl in protected mode","id":"CVE-2026-98470","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":"KVM: SEV: Do cache maintenance on the source VM during intra-host migration","id":"CVE-2026-98471"},"packages":[],"prev":{"headline":"KVM: arm64: Fix AArch32 DBGBXVR\u003cn\u003e handling","id":"CVE-2026-98469"},"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 local attacker can crash a protected KVM host by triggering a kernel warning via an unknown ioctl, causing a panic if panic_on_warn is enabled.","url":"https://insights.sbomify.com/CVE-2026-98470/"}