Live › vulnerability › CVE-2026-98714
Go to dashboardThe Linux kernel's KVM AMD SVM code updated VMCB control fields on VM exit even when VMRUN had failed, where AMD says those actions may not have been performed. The sources do not state what an attacker gains from this.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Hosts running Linux with KVM on AMD processors using SVM, where guest virtual machines are run. Systems without KVM on AMD hardware are not affected by this code path. The sources do not say what triggers the flaw or what a guest or attacker can do with it.
No product ranges from the sources yet.
uname -r to see the running kernel versionlsmod | grep kvm_amdEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98714")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.