cbcvebase.
CVE-2026-45987
published 2026-05-27

CVE-2026-45987: 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…

medium5.5
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.

Affected

10 ranges
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 0c1f74d8b74d8a31751fb6ea5417e48e02c93b580c1f74d8b74d8a31751fb6ea5417e48e02c93b58
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 4b44aa1a134e499c4517597118378b308602a16c4b44aa1a134e499c4517597118378b308602a16c
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < e39a77a9b1e17d2d831c304eafac4c41a784a0bee39a77a9b1e17d2d831c304eafac4c41a784a0be
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 1709418535a8df95532999d61b03d599752802581709418535a8df95532999d61b03d59975280258
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 2f950eeb27af6885416232761700b8820cae0a612f950eeb27af6885416232761700b8820cae0a61
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 497f6af9679fc9c6ce2f438e11ed5d51b1aa8297497f6af9679fc9c6ce2f438e11ed5d51b1aa8297
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < e0377e52f3c10ee572732d11b04625b7f517a862e0377e52f3c10ee572732d11b04625b7f517a862
linuxlinux>= cc440cdad5b7a4c1de12dace725209eb3e0cf663 < 03bee264f8ebfd39e0254c98e112d033a7aa905503bee264f8ebfd39e0254c98e112d033a7aa9055
linuxlinux_kernel