CVE-2026-74607

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-22. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock

Interaction between KVM_CAP_VM_MOVE_ENC_CONTEXT_FROM and KVM_CAP_VM_COPY_ENC_CONTEXT_FROM can cause two separate issues:

  • in sev_migrate_from(), when the destination KVM is a mirror, the mirror
entry is moved from the source's list to the owner's mirror_vms list, without holding the owner's lock unlike other writers of the owner's mirror list (sev_vm_copy_enc_context_from(), sev_vm_destroy()). A concurrent COPY or destroy can race with sev_migrate_from() and corrupt the list.
  • In sev_vm_destroy(), the *owner* is still active and could receive
concurrently a KVM_CAP_VM_MOVE_ENC_CONTEXT_FROM that causes sev->enc_context_owner to change. In this case the incorrect VM receives kvm_put_kvm().

The second issue needs particular care because the owner could disappear altogether (even though the race window is impossibly small) between reading it and locking it. There is thus no way to perform the checks under the owner lock without putting struct kvm under SLAB_TYPESAFE_BY_RCU (which would allow kvm_get_kvm_safe() under RCU critical section).

It is much simpler to just use a global lock, since the critical sections are so small and the new lock is always a leaf lock.

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

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (6)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d78d33275ef2a16c6d080910b291d0a97a0e613
generic

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47976eaaf0a4eb46dade48b3246779090db9e3ec
generic

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/328ab4fabe05af004d886659f8744076e320ddce
generic

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28afde1edbd8b20058cbf4d75fb57876471ec334
generic

KVM: SVM: Serialize accesses to the owner and mirror list with separate lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7943ec3a6d0e7e0a2eb4943300bce089ac3e8c3e

Vendor Advisories for CVE-2026-74607(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 32× 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.

  1. 2026-08-30 02:00 UTCEG score recompute
  2. 2026-08-30 02:00 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 13:30 UTCGHSA enrichment
  5. 2026-08-29 00:56 UTCEG score recompute
  6. 2026-08-29 00:56 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 09:33 UTCGHSA enrichment
  9. 2026-08-27 20:58 UTCEG score recompute
  10. 2026-08-27 20:58 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 08:29 UTCGHSA enrichment
  13. 2026-08-26 19:59 UTCEG score recompute
  14. 2026-08-26 19:58 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 07:29 UTCGHSA enrichment
  17. 2026-08-25 18:59 UTCEG score recompute
  18. 2026-08-25 18:59 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:30 UTCEG score recompute
  21. 2026-08-25 06:30 UTCGHSA enrichment
  22. 2026-08-25 05:45 UTCEG score recompute▲ 8.80
  23. 2026-08-25 05:45 UTCGHSA enrichment
  24. 2026-08-25 05:45 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 7 more
  1. 2026-08-23 13:19 UTCGHSA enrichment
  2. 2026-08-23 13:19 UTCNVD update
  3. 2026-08-23 13:06 UTCGHSA enrichment
  4. 2026-08-23 13:05 UTCMITRE cvelistV5
  5. 2026-08-22 16:24 UTCNVD update
  6. 2026-08-22 15:42 UTCEG score recompute
  7. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74607?
CVE-2026-74607 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Serialize accesses to the owner and mirror list with separate lock Interaction between KVMCAPVMMOVEENCCONTEXTFROM and KVMCAPVMCOPYENCCONTEXTFROM can cause two separate issues: in sevmigratefrom(), when the destination KVM…
When was CVE-2026-74607 disclosed?
CVE-2026-74607 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74607 actively exploited?
CVE-2026-74607 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-74607?
CVE-2026-74607 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74607?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74607, 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

Explore the affected products and dependency analysis for CVE-2026-74607

Explore →

Is Your Infrastructure Affected by CVE-2026-74607?

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

Start Free Scan →Browse All CVEs