# CVE-2026-98714: KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded

> A flaw in Linux KVM SVM handling could lead to undefined behavior or instability when VMRUN fails, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-109233, BELL-CVE-2026-98714, DEBIAN-CVE-2026-98714, GHSA-rrqj-3q8v-92j9, UBUNTU-CVE-2026-98714

## What is CVE-2026-98714?

CVE-2026-98714 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98714?


## How do I fix CVE-2026-98714?

Apply the vendor's patch.

## Is CVE-2026-98714 being exploited?

There is no known exploitation of CVE-2026-98714 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98714 and fix it if it is affected.

What it is: CVE-2026-98714 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98714 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98714/ (Markdown: https://insights.sbomify.com/CVE-2026-98714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98714
- OSV: https://osv.dev/vulnerability/CVE-2026-98714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98714/
Summaries are generated and may contain mistakes; the official description above is the record.