<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 12 Nov 2026 06:56:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98468 — KVM: arm64: Fix spurious warning for benign stage 2 teardown race</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: Fix spurious warning for benign stage 2 teardown race&lt;/p&gt;
&lt;p&gt;kvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an
L2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB
of RAM, all of which was then exited.&lt;/p&gt;
&lt;p&gt;Under memory pressure in the L0 host warnings were observed due to
migration triggered by compaction:&lt;/p&gt;
&lt;p&gt;WARNING: arch/arm64/kvm/mmu.c:336 at __unmap_stage2_range+0x64/0x80,
CPU#5: kcompactd0/66&lt;/p&gt;
&lt;p&gt;Which was, in turn, triggered by an MMU notifier for the host invalidation:&lt;/p&gt;
&lt;p&gt;mmu_notifier_invalidate_range_start()
  -&amp;gt; ... -&amp;gt; kvm_mmu_notifier_invalidate_range_start()
    -&amp;gt; kvm_mmu_unmap_gfn_range()
      -&amp;gt; kvm_unmap_gfn_range()
        -&amp;gt; kvm_nested_s2_unmap()
          -&amp;gt; kvm_stage2_unmap_range()
            -&amp;gt; __unmap_stage2_range()
               -&amp;gt; stage2_apply_range()
       	       &amp;lt;- -EINVAL, triggering a WARN_ON()&lt;/p&gt;
&lt;p&gt;Racing with L0&amp;#39;s teardown of stage 2 page tables:&lt;/p&gt;
&lt;p&gt;exit_mm()
  -&amp;gt; mmput()
    -&amp;gt; __mmput()
      -&amp;gt; exit_mmap()
        -&amp;gt; mmu_notifier_release()
	  -&amp;gt; ... -&amp;gt; kvm_mmu_notifier_release()
            -&amp;gt; kvm_flush_shadow_all()
              -&amp;gt; kvm_arch_flush_shadow_all()
	        -&amp;gt; kvm_free_stage2_pgd()
		  -&amp;gt; [ acquire kvm-&amp;gt;mmu_lock for write ]
		  -&amp;gt; mmu-&amp;gt;pgt = NULL [ among other tasks ]
		  -&amp;gt; [ release kvm-&amp;gt;mmu_lock for write ]&lt;/p&gt;
&lt;p&gt;It turns out there is a benign race resulting in a spurious warning:&lt;/p&gt;
&lt;p&gt;Thread A - notify: migration   | Thread B…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: Fix spurious warning for benign stage 2 teardown race&lt;/p&gt;
&lt;p&gt;kvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an
L2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB
of RAM, all of which was then exited.&lt;/p&gt;
&lt;p&gt;Under memory pressure in the L0 host warnings were observed due to
migration triggered by compaction:&lt;/p&gt;
&lt;p&gt;WARNING: arch/arm64/kvm/mmu.c:336 at __unmap_stage2_range+0x64/0x80,
CPU#5: kcompactd0/66&lt;/p&gt;
&lt;p&gt;Which was, in turn, triggered by an MMU notifier for the host invalidation:&lt;/p&gt;
&lt;p&gt;mmu_notifier_invalidate_range_start()
  -&amp;gt; ... -&amp;gt; kvm_mmu_notifier_invalidate_range_start()
    -&amp;gt; kvm_mmu_unmap_gfn_range()
      -&amp;gt; kvm_unmap_gfn_range()
        -&amp;gt; kvm_nested_s2_unmap()
          -&amp;gt; kvm_stage2_unmap_range()
            -&amp;gt; __unmap_stage2_range()
               -&amp;gt; stage2_apply_range()
       	       &amp;lt;- -EINVAL, triggering a WARN_ON()&lt;/p&gt;
&lt;p&gt;Racing with L0&amp;#39;s teardown of stage 2 page tables:&lt;/p&gt;
&lt;p&gt;exit_mm()
  -&amp;gt; mmput()
    -&amp;gt; __mmput()
      -&amp;gt; exit_mmap()
        -&amp;gt; mmu_notifier_release()
	  -&amp;gt; ... -&amp;gt; kvm_mmu_notifier_release()
            -&amp;gt; kvm_flush_shadow_all()
              -&amp;gt; kvm_arch_flush_shadow_all()
	        -&amp;gt; kvm_free_stage2_pgd()
		  -&amp;gt; [ acquire kvm-&amp;gt;mmu_lock for write ]
		  -&amp;gt; mmu-&amp;gt;pgt = NULL [ among other tasks ]
		  -&amp;gt; [ release kvm-&amp;gt;mmu_lock for write ]&lt;/p&gt;
&lt;p&gt;It turns out there is a benign race resulting in a spurious warning:&lt;/p&gt;
&lt;p&gt;Thread A - notify: migration   | Thread B…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98468</guid>
    </item>
  </channel>
</rss>
