# CVE-2026-46059: KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN

> A logic error in KVM nested virtualization handling of NextRIP can cause incorrect state restoration, potentially leading to guest instability or denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 27 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-88685, BELL-CVE-2026-46059, DEBIAN-CVE-2026-46059, GHSA-fhch-vffp-hj8x, ROOT-OS-DEBIAN-11-CVE-2026-46059, ROOT-OS-DEBIAN-12-CVE-2026-46059, ROOT-OS-DEBIAN-13-CVE-2026-46059, ROOT-OS-UBUNTU-2204-CVE-2026-46059, ROOT-OS-UBUNTU-2404-CVE-2026-46059, UBUNTU-CVE-2026-46059

## What is CVE-2026-46059?

CVE-2026-46059 is a medium-severity vulnerability in Linux kernel, published on 27 May 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: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN

For guests with NRIPS disabled, L1 does not provide NextRIP when running
an L2 with an injected soft interrupt, instead it advances the current RIP
before running it. KVM uses the current RIP as the NextRIP in vmcb02 to
emulate a CPU without NRIPS.

However, after L2 runs the first time, NextRIP will be updated by the CPU
and/or KVM, and the current RIP is no longer the correct value to use in
vmcb02.  Hence, after save/restore, use the current RIP if and only if a
nested run is pending, otherwise use NextRIP.  Give soft_int_next_rip the
same treatment, as it's the same logic, just for a narrower use case.

[sean: give soft_int_next_rip the same treatment]

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-46059 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46059 is a medium-severity vulnerability in Linux kernel, published on 27 May 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-46059 in the wild and no public exploit code.

Affected product: Linux kernel. 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-46059/ (Markdown: https://insights.sbomify.com/CVE-2026-46059/index.md)
```

## Sources

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

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