{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98468 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98468 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-98468 and fix it if it is affected.\n\nWhat it is: CVE-2026-98468 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-98468 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-98468/ (Markdown: https://insights.sbomify.com/CVE-2026-98468/index.md)","id":"CVE-2026-98468","markdown":"https://insights.sbomify.com/CVE-2026-98468/index.md","name":"CVE-2026-98468","record":{"aliases":["BELL-CVE-2026-98468","DEBIAN-CVE-2026-98468","GHSA-5gcw-m9q3-vcxx","UBUNTU-CVE-2026-98468"],"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":"none","summary":"A race condition in Linux KVM arm64 stage 2 teardown can trigger spurious kernel warnings, potentially leading to denial of service under memory pressure.","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: arm64: Fix spurious warning for benign stage 2 teardown race\n\nkvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an\nL2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB\nof RAM, all of which was then exited.\n\nUnder memory pressure in the L0 host warnings were observed due to\nmigration triggered by compaction:\n\nWARNING: arch/arm64/kvm/mmu.c:336 at __unmap_stage2_range+0x64/0x80,\nCPU#5: kcompactd0/66\n\nWhich was, in turn, triggered by an MMU notifier for the host invalidation:\n\nmmu_notifier_invalidate_range_start()\n  -\u003e ... -\u003e kvm_mmu_notifier_invalidate_range_start()\n    -\u003e kvm_mmu_unmap_gfn_range()\n      -\u003e kvm_unmap_gfn_range()\n        -\u003e kvm_nested_s2_unmap()\n          -\u003e kvm_stage2_unmap_range()\n            -\u003e __unmap_stage2_range()\n               -\u003e stage2_apply_range()\n       \t       \u003c- -EINVAL, triggering a WARN_ON()\n\nRacing with L0's teardown of stage 2 page tables:\n\nexit_mm()\n  -\u003e mmput()\n    -\u003e __mmput()\n      -\u003e exit_mmap()\n        -\u003e mmu_notifier_release()\n\t  -\u003e ... -\u003e kvm_mmu_notifier_release()\n            -\u003e kvm_flush_shadow_all()\n              -\u003e kvm_arch_flush_shadow_all()\n\t        -\u003e kvm_free_stage2_pgd()\n\t\t  -\u003e [ acquire kvm-\u003emmu_lock for write ]\n\t\t  -\u003e mmu-\u003epgt = NULL [ among other tasks ]\n\t\t  -\u003e [ release kvm-\u003emmu_lock for write ]\n\nIt turns out there is a benign race resulting in a spurious warning:\n\n\tThread A - notify: migration   | Thread B - notify: release\n\t-------------------------------|---------------------------------\n\t\u003c kvm-\u003emmu_lock held \u003e         |\n\tstage2_apply_range()           |\n\t  get mmu-\u003epgt, check !NULL    |\n\t  ...                          | kvm_arch_flush_shadow_all()\n\t  cond_resched_rwlock_write(); |   \u003c contend, sleep kvm-\u003emmu_lock \u003e\n\t\u003c drop kvm-\u003emmu_lock \u003e         |   \u003c acquire kvm-\u003emmu_lock\u003e\n                                       |   ...\n\t\t\t\t       |   kvm_free_stage2_pgd()\n                                       |     mmu-\u003epgt = NULL\n\t\t\t\t       |   \u003c invalidate MMU \u003e\n\t\t\t\t       |   ...\n\t\t\t\t       |   \u003c release kvm-\u003emmu_lock \u003e\n\t[ scheduled ]\t\t       |\n\tstage2_apply_range()           |\n\t  \u003c loop to next \u003e             |\n\t  get, mmu-\u003epgt, check !NULL   |\n\t  is NULL, return -EINVAL      |\n        __unmap_stage2_range()         |\n\t  WARN_ON(-EINVAL) \u003c--- entirely spurious - the race was handled\n                                 correctly.\n\nFix the spurious warning by updating stage2_apply_range() to no longer\ntreat concurrent PGT teardown on lock release as an error - whether the\nwalker is tearing down page tables or doing something else this is a\nlegitimate reason to abort the operation without error.\n\nThis keeps the warning in place for all other circumstances.\n\nIn practice only __unmap_stage2_range() actually does anything with the\nerror so this only impacts that.","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: Fix spurious warning for benign stage 2 teardown race","id":"CVE-2026-98468","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"KVM: arm64: Fix AArch32 DBGBXVR\u003cn\u003e handling","id":"CVE-2026-98469"},"packages":[],"prev":{"headline":"KVM: arm64: nv: Fix null ptr deref on nested wp/unmap, teardown race","id":"CVE-2026-98467"},"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 race condition in Linux KVM arm64 stage 2 teardown can trigger spurious kernel warnings, potentially leading to denial of service under memory pressure.","url":"https://insights.sbomify.com/CVE-2026-98468/"}