{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.170-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()  Add SRCU read-side protection when reading PDPTR registers in __get_sregs2().  Reading PDPTRs may trigger access to guest memory: kvm_pdptr_read() -\u003e svm_cache_reg() -\u003e load_pdptrs() -\u003e kvm_vcpu_read_guest_page() -\u003e kvm_vcpu_gfn_to_memslot()  kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(), which uses srcu_dereference_check() and requires either kvm-\u003esrcu or kvm-\u003eslots_lock to be held. Currently only vcpu-\u003emutex is held, triggering lockdep warning:  ============================= WARNING: suspicious RCU usage in kvm_vcpu_gfn_to_memslot 6.12.59+ #3 Not tainted  include/linux/kvm_host.h:1062 suspicious rcu_dereference_check() usage!  other info that might help us debug this:  rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.5.1717/15100:  #0: ff1100002f4b00b0 (\u0026vcpu-\u003emutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590  Call Trace:  \u003cTASK\u003e  __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/kvm/x86.c:1065  svm_cache_reg+0x1c9/0x230 arch/x86/kvm/svm/svm.c:1688  kvm_pdptr_read arch/x86/kvm/kvm_cache_regs.h:141 [inline]  __get_sregs2 arch/x86/kvm/x86.c:11784 [inline]  kvm_arch_vcpu_ioctl+0x3e20/0x4aa0 arch/x86/kvm/x86.c:6279  kvm_vcpu_ioctl+0x856/0x1590 virt/kvm/kvm_main.c:4663  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl fs/ioctl.c:893 [inline]  __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:893  do_syscall_x64 arch/x86/entry/common.c:52 [inline]  do_syscall_64+0xbd/0x1d0 arch/x86/entry/common.c:83  entry_SYSCALL_64_after_hwframe+0x77/0x7f  Found by Linux Verification Center (linuxtesting.org) with Syzkaller.",
  "id": "DEBIAN-CVE-2026-43214",
  "modified": "2026-09-14T16:47:37.808550884Z",
  "published": "2026-05-06T12:16:40.920Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43214"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-43214"
  ]
}