{"id":40940,"date":"2026-10-19T00:31:37","date_gmt":"2026-10-18T16:31:37","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98468"},"modified":"2026-10-19T00:31:37","modified_gmt":"2026-10-18T16:31:37","slug":"cve-2026-98468","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-98468","title":{"rendered":"CVE-2026-98468 &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Fix spuri"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>KVM: arm64: Fix spurious warning for benign stage 2 teardown race<\/p>\n<p>kvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an<br \/>\nL2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB<br \/>\nof RAM, all of which was then exited.<\/p>\n<p>Under memory pressure in the L0 host warnings were observed due to<br \/>\nmigration triggered by compaction:<\/p>\n<p>WARNING: arch\/arm64\/kvm\/mmu.c:336 at __unmap_stage2_range+0x64\/0x80,<br \/>\nCPU#5: kcompactd0\/66<\/p>\n<p>Which was, in turn, triggered by an MMU notifier for the host invalidation:<\/p>\n<p>mmu_notifier_invalidate_range_start()<br \/>\n  -&gt; &#8230; -&gt; kvm_mmu_notifier_invalidate_range_start()<br \/>\n    -&gt; kvm_mmu_unmap_gfn_range()<br \/>\n      -&gt; kvm_unmap_gfn_range()<br \/>\n        -&gt; kvm_nested_s2_unmap()<br \/>\n          -&gt; kvm_stage2_unmap_range()<br \/>\n            -&gt; __unmap_stage2_range()<br \/>\n               -&gt; stage2_apply_range()<br \/>\n       \t        mmput()<br \/>\n    -&gt; __mmput()<br \/>\n      -&gt; exit_mmap()<br \/>\n        -&gt; mmu_notifier_release()<br \/>\n\t  -&gt; &#8230; -&gt; kvm_mmu_notifier_release()<br \/>\n            -&gt; kvm_flush_shadow_all()<br \/>\n              -&gt; kvm_arch_flush_shadow_all()<br \/>\n\t        -&gt; kvm_free_stage2_pgd()<br \/>\n\t\t  -&gt; [ acquire kvm-&gt;mmu_lock for write ]<br \/>\n\t\t  -&gt; mmu-&gt;pgt = NULL [ among other tasks ]<br \/>\n\t\t  -&gt; [ release kvm-&gt;mmu_lock for write ]<\/p>\n<p>It turns out there is a benign race resulting in a spurious warning:<\/p>\n<p>\tThread A &#8211; notify: migration   | Thread B &#8211; notify: release<br \/>\n\t&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-|&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br \/>\n\tmmu_lock held &gt;         |<br \/>\n\tstage2_apply_range()           |<br \/>\n\t  get mmu-&gt;pgt, check !NULL    |<br \/>\n\t  &#8230;                          | kvm_arch_flush_shadow_all()<br \/>\n\t  cond_resched_rwlock_write(); |   mmu_lock &gt;<br \/>\n\tmmu_lock &gt;         |   mmu_lock&gt;<br \/>\n                                       |   &#8230;<br \/>\n\t\t\t\t       |   kvm_free_stage2_pgd()<br \/>\n                                       |     mmu-&gt;pgt = NULL<br \/>\n\t\t\t\t       |<br \/>\n\t\t\t\t       |   &#8230;<br \/>\n\t\t\t\t       |   mmu_lock &gt;<br \/>\n\t[ scheduled ]\t\t       |<br \/>\n\tstage2_apply_range()           |<br \/>\n\t               |<br \/>\n\t  get, mmu-&gt;pgt, check !NULL   |<br \/>\n\t  is NULL, return -EINVAL      |<br \/>\n        __unmap_stage2_range()         |<br \/>\n\t  WARN_ON(-EINVAL) &lt;&#8212; entirely spurious &#8211; the race was handled<br \/>\n                                 correctly.<\/p>\n<p>Fix the spurious warning by updating stage2_apply_range() to no longer<br \/>\ntreat concurrent PGT teardown on lock release as an error &#8211; whether the<br \/>\nwalker is tearing down page tables or doing something else this is a<br \/>\nlegitimate reason to abort the operation without error.<\/p>\n<p>This keeps the warning in place for all other circumstances.<\/p>\n<p>In practice only __unmap_stage2_range() actually does anything with the<br \/>\nerror so this only impacts that.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>KVM: arm64: Fix spurious warning for benign stage 2 teardown race<\/p>\n<p>kvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB <\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-40940","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/40940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=40940"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=40940"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=40940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}