CVE-2026-45987

MEDIUM EPSS 2.4%
Published May 27, 20261mo ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published May 27, 2026 1mo ago
Last Modified Jun 17, 2026 1w ago

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Sync interrupt shadow to cached vmcb12 after VMRUN of L2 After VMRUN in guest mode, nested_sync_control_from_vmcb02() syncs fields written by the CPU from vmcb02 to the cached vmcb12. This is because the cached vmcb12 is used as the authoritative copy of some of the controls, and is the payload when saving/restoring nested state. int_state is also written by the CPU, specifically bit 0 (i.e. SVM_INTERRUPT_SHADOW_MASK) for nested VMs, but it is not sync'd to cached vmcb12. This does not cause a problem if KVM_SET_NESTED_STATE preceeds KVM_SET_VCPU_EVENTS in the restore path, as an interrupt shadow would be correctly restored to vmcb02 (KVM_SET_VCPU_EVENTS overwrites what KVM_SET_NESTED_STATE restored in int_state). However, if KVM_SET_VCPU_EVENTS preceeds KVM_SET_NESTED_STATE, an interrupt shadow would be restored into vmcb01 instead of vmcb02. This would mostly be benign for L1 (delays an interrupt), but not for L2. For L2, the vCPU could hang (e.g. if a wakeup interrupt is delivered before a HLT that should have been in an interrupt shadow). Sync int_state to the cached vmcb12 in nested_sync_control_from_vmcb02() to avoid this problem. With that, KVM_SET_NESTED_STATE restores the correct interrupt shadow state, and if KVM_SET_VCPU_EVENTS follows it would overwrite it with the same value.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
2.4% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Affected Products 7

VendorProductVersionRange
linuxlinux_kernel*≥5.8  –  <5.10.258
linuxlinux_kernel*≥5.11  –  <5.15.209
linuxlinux_kernel*≥5.16  –  <6.1.175
linuxlinux_kernel*≥6.2  –  <6.6.140
linuxlinux_kernel*≥6.7  –  <6.12.86
linuxlinux_kernel*≥6.13  –  <6.18.27
linuxlinux_kernel*≥6.19  –  <7.0.4

References 8

  • git.kernel.org https://git.kernel.org/stable/c/03bee264f8ebfd39e0254c98e112d033a7aa9055
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/0c1f74d8b74d8a31751fb6ea5417e48e02c93b58
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/1709418535a8df95532999d61b03d59975280258
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2f950eeb27af6885416232761700b8820cae0a61
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/497f6af9679fc9c6ce2f438e11ed5d51b1aa8297
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/4b44aa1a134e499c4517597118378b308602a16c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e0377e52f3c10ee572732d11b04625b7f517a862
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e39a77a9b1e17d2d831c304eafac4c41a784a0be
    Patch

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/03bee264f8ebfd39e0254c98e112d033a7aa9055
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/0c1f74d8b74d8a31751fb6ea5417e48e02c93b58
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/1709418535a8df95532999d61b03d59975280258
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2f950eeb27af6885416232761700b8820cae0a61
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/497f6af9679fc9c6ce2f438e11ed5d51b1aa8297
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/4b44aa1a134e499c4517597118378b308602a16c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e0377e52f3c10ee572732d11b04625b7f517a862
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e39a77a9b1e17d2d831c304eafac4c41a784a0be
    Patch