Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74607KVM: SVM: Serialize accesses to the owner and mirror list with separate lock

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 55 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74607, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < 7943ec3a6d0e7e0a2eb4943300bce089ac3e8c3e
    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < 28afde1edbd8b20058cbf4d75fb57876471ec334
    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < 328ab4fabe05af004d886659f8744076e320ddce
    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < 47976eaaf0a4eb46dade48b3246779090db9e3ec
    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < d728baba0f20e49439fc7831bf3e4e7dee82161a
    • affected b2125513dfc0dd0ec5a9605138a3c356592cfb73 – < 1d78d33275ef2a16c6d080910b291d0a97a0e613
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74607 badge
[![CVE-2026-74607](https://cveledger.app/badge/CVE-2026-74607.svg)](https://cveledger.app/cve/CVE-2026-74607)

Record last updated .