All vulnerabilities

Servers and applications

CVE-2026-46059

KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN

Severity
Unrated
Published
27 May 2026
Last changed
6 Nov 2026
Added to UpHeron
30 Oct 2026
Fixed in
6.1.191, 6.6.160, 6.12.114, 6.18.27, 7.0.4
Exploit chance
0.1% in the next 30 daysHigher than 2% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

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]

From the CVE Program.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 5.8 before 6.1.191
  • From 6.2 before 6.6.160
  • From 6.7 before 6.12.114
  • From 6.13 before 6.18.27
  • From 6.19 before 7.0.4

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-46059