Riskcovery

CVE-2026-46059

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

State
Published
Severity
Not scored
Published
May 27, 2026
Updated
Oct 30, 2026
Reserved
May 13, 2026

Read the record on cve.org

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]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before 98717fb482fa269db491f7c84aec777d3aeb2cd1Affected
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fcAffected
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before f9197a9dd1408e203147326139122f9c5312ce9cAffected
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bbAffected
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before 69fe1411a5ce678b4da6489b5d2282b4e1d13acfAffected
  • cc440cdad5b7a4c1de12dace725209eb3e0cf663 to before 8d397582f6b5e9fbcf09781c7c934b4910e94a50Affected
LinuxLinux
  • 5.8Affected
  • before 5.8Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.27 through 6.18.*Not affected
  • 7.0.4 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.