Answer in brief
CVE-2026-46059 records a Unknown severity vulnerability in KVM: nSVM: Always use NextRIP as vmcb02's NextRIP after first L2 VMRUN. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.8 | Not reported |
| Linux/Linuxgeneric | >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc || >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <f9197a9dd1408e203147326139122f9c5312ce9c || >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb || >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <69fe1411a5ce678b4da6489b5d2282b4e1d13acf || >=cc440cdad5b7a4c1de12dace725209eb3e0cf663 <8d397582f6b5e9fbcf09781c7c934b4910e94a50 | b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc, f9197a9dd1408e203147326139122f9c5312ce9c, 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb, 69fe1411a5ce678b4da6489b5d2282b4e1d13acf, 8d397582f6b5e9fbcf09781c7c934b4910e94a50 |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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]
Quoted source text, attributed separately from HOL analysis.