{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98717 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98717 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-98717 and fix it if it is affected.\n\nWhat it is: CVE-2026-98717 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-98717 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-98717/ (Markdown: https://insights.sbomify.com/CVE-2026-98717/index.md)","id":"CVE-2026-98717","markdown":"https://insights.sbomify.com/CVE-2026-98717/index.md","name":"CVE-2026-98717","record":{"aliases":["AZL-109349","BELL-CVE-2026-98717","DEBIAN-CVE-2026-98717","GHSA-hf2p-vjqm-2xw6","UBUNTU-CVE-2026-98717"],"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 race condition in KVM shadow page table walks causes a kernel NULL pointer dereference, leading to a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: x86/mmu: Bail from shadow walks if the root is invalid or a dummy\n\nWhen walking shadow page tables, immediately terminate the walk if the root\nis a \"dummy\" root, i.e. a root whose top-level page table is backed by the\nzero page, but otherwise doesn't exist.  If memslot creation races with a\nstage-2 page fault (EPT violation or #NPF) from L2, then if the stars align,\nKVM will attempt to walk shadow page tables using the zero page and hit a\nNULL pointer deref.\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000021\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 30 UID: 1000 PID: 941 Comm: qemu Not tainted 7.2.0-rc2-1b731e5ded48-next-vm #1741 PREEMPTLAZY\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:__kvm_mmu_invalidate_addr+0xea/0x210 [kvm]\n  Call Trace:\n   \u003cTASK\u003e\n   kvm_mmu_invalidate_addr+0x92/0xe0 [kvm]\n   __kvm_inject_emulated_page_fault+0x67/0x80 [kvm]\n   ept_page_fault+0x160/0x850 [kvm]\n   kvm_mmu_do_page_fault+0x102/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8e/0x6b0 [kvm]\n   vmx_handle_exit+0x163/0x640 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0x960/0x2120 [kvm]\n   kvm_vcpu_ioctl+0x2c7/0x970 [kvm]\n   __x64_sys_ioctl+0x90/0xd0\n   do_syscall_64+0x67/0x5f0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f606d0b53bb\n\nOpportunistically harden the shadow walks against fully invalid roots, but\nWARN, as all callers are expected/required to pre-check for a valid root.\nDon't WARN in the dummy root case as the whole point of using a dummy root\nis to provide a root that's valid enough to enter the guest, i.e. it should\nJust Work for all flows except those that *need* to know about dummy roots.\n\nAlternatively, KVM could allocate a dedicated page and associated shadow\npage structure for the dummy root, which is very tempting as it such an\napproach should be more resilient against unexpected behavior.  But that\nwould be a much larger and thus riskier change than simply terminating\nwalks of dummy roots.","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: x86/mmu: Bail from shadow walks if the root is invalid or a dummy","id":"CVE-2026-98717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state","id":"CVE-2026-98718"},"packages":[],"prev":{"headline":"KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted","id":"CVE-2026-98716"},"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-21","vendors":["Linux"]},"summary":"A race condition in KVM shadow page table walks causes a kernel NULL pointer dereference, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-98717/"}