CVE-2026-46071

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12

svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined.

Move vmcb_mark_dirty() to callers and drop it for vmcb12.

This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9efe23568806d1cd06f7d146f9b3037b8d585a9f

Vendor Advisories for CVE-2026-46071(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu

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 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 67× 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 195 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46071?
CVE-2026-46071 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 svmcopylbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nestedsvmvmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally…
When was CVE-2026-46071 disclosed?
CVE-2026-46071 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46071 actively exploited?
CVE-2026-46071 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-46071?
CVE-2026-46071 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46071, 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-46071

Explore →

Is Your Infrastructure Affected by CVE-2026-46071?

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

Start Free Scan →Browse All CVEs