CVE-2026-46059
MediumCVSS 5.5Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
A vulnerability in the Linux kernel has been resolved in KVM regarding the use of NextRIP in vmcb02 after the first L2 VMRUN. The issue occurs when NRIPS is disabled, leading to incorrect NextRIP settings.
Risk Assessment
Organizations may face issues with CPU emulation in virtual environments, potentially leading to unpredictable system behavior and security vulnerabilities.
Recommendation
It is recommended to update the Linux kernel to the latest version to patch this vulnerability and ensure proper CPU emulation in KVM environments.
Original NVD description (English source)
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]