Skip to content
statance
MenuClose
unknown

CVE-2026-98714

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

Published 18 Oct 2026 · Source updated 10 Nov 2026 · Retrieved 2026-11-19 15:38 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 8d28fec406e4d5ce6c109fe12699976e72e9748e to < 2e9b8c79ae6c1dcf650ea288cf8fc69ee5241dd9; affected: 8d28fec406e4d5ce6c109fe12699976e72e9748e to < 5d06e2f861d61a03481348378fdf9cc3e68bff47; affected: 8d28fec406e4d5ce6c109fe12699976e72e9748e to < 8676b29d186fcb5c1251d8152fc91d19421e5600; affected: 8d28fec406e4d5ce6c109fe12699976e72e9748e to < e27fc915c8f575ab5630e27d97465c2077d4b9d1See vendor advisory
LinuxLinuxaffected: 2.6.38; unaffected: 0 to < 2.6.38; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.10 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed