CVE-2026-43214

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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() -> svm_cache_reg() -> load_pdptrs() -> kvm_vcpu_read_guest_page() -> kvm_vcpu_gfn_to_memslot()

kvm_vcpu_gfn_to_memslot() dereferences memslots via __kvm_memslots(), which uses srcu_dereference_check() and requires either kvm->srcu or kvm->slots_lock to be held. Currently only vcpu->mutex 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 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d5/0x1590

Call Trace: __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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f621ca24f9f489e226e22560761b04884984133b
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b33f8d816950b10e7879cd8ffd7ae4b649ada4db
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f2bfea51151dfbb24b52f452eb3d5f5fe0e506e
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95d848dc7e639988dbb385a8cba9b484607cf98c
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/708e20c66b2761d878a2bc3c7534e7f814e4dec5
generic

KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57536ff0a6bd69a5808d682925202babdb5ddc13

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 210 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 16:23 UTCOSV refresh
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:12 UTCEPSS rescore
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-23 20:01 UTCEG score recompute
  18. 2026-08-23 20:01 UTCVendor advisory
  19. 2026-08-23 20:01 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 12:55 UTCEG score recompute
Show 75 more
  1. 2026-08-17 12:55 UTCVendor advisory
  2. 2026-08-17 12:55 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 04:53 UTCEG score recompute
  5. 2026-08-16 04:53 UTCVendor advisory
  6. 2026-08-16 04:53 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 15:32 UTCVendor advisory
  10. 2026-08-14 15:32 UTCGHSA enrichment
  11. 2026-08-14 03:27 UTCEG score recompute
  12. 2026-08-14 03:27 UTCVendor advisory
  13. 2026-08-14 03:27 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 06:07 UTCVendor advisory
  16. 2026-08-13 06:07 UTCGHSA enrichment
  17. 2026-08-12 17:01 UTCEG score recompute
  18. 2026-08-12 17:01 UTCVendor advisory
  19. 2026-08-12 17:00 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 16:00 UTCEG score recompute
  22. 2026-08-11 16:00 UTCVendor advisory
  23. 2026-08-11 16:00 UTCGHSA enrichment
  24. 2026-08-11 13:43 UTCEPSS rescore
  25. 2026-08-11 01:31 UTCEG score recompute
  26. 2026-08-11 01:31 UTCVendor advisory
  27. 2026-08-11 01:31 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 02:46 UTCVendor advisory
  30. 2026-08-10 02:46 UTCGHSA enrichment
  31. 2026-08-09 14:40 UTCEG score recompute
  32. 2026-08-09 14:40 UTCVendor advisory
  33. 2026-08-09 14:40 UTCGHSA enrichment
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 02:35 UTCEG score recompute
  36. 2026-08-09 02:35 UTCVendor advisory
  37. 2026-08-09 02:35 UTCGHSA enrichment
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 11:08 UTCVendor advisory
  40. 2026-08-08 11:07 UTCGHSA enrichment
  41. 2026-08-07 23:02 UTCEG score recompute
  42. 2026-08-07 23:02 UTCVendor advisory
  43. 2026-08-07 23:02 UTCGHSA enrichment
  44. 2026-08-07 10:57 UTCVendor advisory
  45. 2026-08-07 10:57 UTCGHSA enrichment
  46. 2026-08-06 16:54 UTCEG score recompute
  47. 2026-08-06 16:54 UTCVendor advisory
  48. 2026-08-06 16:54 UTCGHSA enrichment
  49. 2026-08-06 13:46 UTCEPSS rescore
  50. 2026-08-06 01:56 UTCEG score recompute
  51. 2026-08-06 01:56 UTCVendor advisory
  52. 2026-08-06 01:56 UTCGHSA enrichment
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-05 13:51 UTCEG score recompute
  55. 2026-08-05 13:51 UTCVendor advisory
  56. 2026-08-05 13:51 UTCGHSA enrichment
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:38 UTCEPSS rescore
  59. 2026-08-03 19:52 UTCEG score recompute
  60. 2026-08-03 19:52 UTCVendor advisory
  61. 2026-08-03 19:52 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 17:13 UTCVendor advisory
  64. 2026-08-02 17:13 UTCGHSA enrichment
  65. 2026-08-02 05:07 UTCEG score recompute
  66. 2026-08-02 05:07 UTCVendor advisory
  67. 2026-08-02 05:07 UTCGHSA enrichment
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-07-30 16:28 UTCEPSS rescore
  71. 2026-07-30 01:30 UTCEPSS rescore
  72. 2026-07-28 15:36 UTCEPSS rescore
  73. 2026-07-27 14:13 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43214?
CVE-2026-43214 is a high vulnerability published on May 6, 2026. 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: kvmpdptrread() -> svmcachereg() ->…
When was CVE-2026-43214 disclosed?
CVE-2026-43214 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43214 actively exploited?
CVE-2026-43214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-43214?
CVE-2026-43214 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43214, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43214

Explore →

Is Your Infrastructure Affected by CVE-2026-43214?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.