All reports
Medium

kernel: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98714

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD: there's no explicit architectural guarantee about the behavior in the presence of VMRUN failures. So the best thing to do would be to assume that if VMRUN fails, the actions requested in the control fields may not have been performed.

A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem for AMD processors (SVM). When virtual machine execution fails, the hypervisor prematurely updates control fields and marks control blocks as clean, assuming hardware operations were performed. A local attacker could leverage this behavior to cause state desynchronization between KVM and the processor, leading to system instability or unexpected guest behavior.