<?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://vulnerability.circl.lu</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>Wed, 30 Sep 2026 23:23:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43214 — KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43214</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: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()&lt;/p&gt;
&lt;p&gt;Add SRCU read-side protection when reading PDPTR registers in
__get_sregs2().&lt;/p&gt;
&lt;p&gt;Reading PDPTRs may trigger access to guest memory:
kvm_pdptr_read() -&amp;gt; svm_cache_reg() -&amp;gt; load_pdptrs() -&amp;gt;
kvm_vcpu_read_guest_page() -&amp;gt; kvm_vcpu_gfn_to_memslot()&lt;/p&gt;
&lt;p&gt;kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(),
which uses srcu_dereference_check() and requires either kvm-&amp;gt;srcu or
kvm-&amp;gt;slots_lock to be held. Currently only vcpu-&amp;gt;mutex is held,
triggering lockdep warning:&lt;/p&gt;
&lt;p&gt;=============================
WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot
6.12.59+ #3 Not tainted&lt;/p&gt;
&lt;p&gt;include/linux/kvm_host.h:1062 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.5.1717/15100:
 #0: ff1100002f4b00b0 (&amp;amp;vcpu-&amp;gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0xf0/0x120 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x1e3/0x270 kernel/locking/lockdep.c:6824
 __kvm_memslots include/linux/kvm_host.h:1062 [inline]
 __kvm_memslots include/linux/kvm_host.h:1059 [inline]
 kvm_vcpu_memslots include/linux/kvm_host.h:1076 [inline]
 kvm_vcpu_gfn_to_memslot+0x518/0x5e0 virt/kvm/kvm_main.c:2617
 kvm_vcpu_read_guest_page+0x27/0x50 virt/kvm/kvm_main.c:3302
 load_pdptrs+0xff/0x4b0 arch/x86/…&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: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()&lt;/p&gt;
&lt;p&gt;Add SRCU read-side protection when reading PDPTR registers in
__get_sregs2().&lt;/p&gt;
&lt;p&gt;Reading PDPTRs may trigger access to guest memory:
kvm_pdptr_read() -&amp;gt; svm_cache_reg() -&amp;gt; load_pdptrs() -&amp;gt;
kvm_vcpu_read_guest_page() -&amp;gt; kvm_vcpu_gfn_to_memslot()&lt;/p&gt;
&lt;p&gt;kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(),
which uses srcu_dereference_check() and requires either kvm-&amp;gt;srcu or
kvm-&amp;gt;slots_lock to be held. Currently only vcpu-&amp;gt;mutex is held,
triggering lockdep warning:&lt;/p&gt;
&lt;p&gt;=============================
WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot
6.12.59+ #3 Not tainted&lt;/p&gt;
&lt;p&gt;include/linux/kvm_host.h:1062 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.5.1717/15100:
 #0: ff1100002f4b00b0 (&amp;amp;vcpu-&amp;gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0xf0/0x120 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x1e3/0x270 kernel/locking/lockdep.c:6824
 __kvm_memslots include/linux/kvm_host.h:1062 [inline]
 __kvm_memslots include/linux/kvm_host.h:1059 [inline]
 kvm_vcpu_memslots include/linux/kvm_host.h:1076 [inline]
 kvm_vcpu_gfn_to_memslot+0x518/0x5e0 virt/kvm/kvm_main.c:2617
 kvm_vcpu_read_guest_page+0x27/0x50 virt/kvm/kvm_main.c:3302
 load_pdptrs+0xff/0x4b0 arch/x86/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43214</guid>
    </item>
  </channel>
</rss>
