Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f9197a9dd1408e203147326139122f9c5312ce9c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f9197a9dd1408e203147326139122f9c5312ce9c, b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc, 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < f9197a9dd1408e203147326139122f9c5312ce9c
Fixed in
  • f9197a9dd1408e203147326139122f9c5312ce9c
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc
Fixed in
  • b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb
Fixed in
  • 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 69fe1411a5ce678b4da6489b5d2282b4e1d13acf
Fixed in
  • 69fe1411a5ce678b4da6489b5d2282b4e1d13acf
LinuxLinuxAffected
  • ≥ cc440cdad5b7a4c1de12dace725209eb3e0cf663, < 8d397582f6b5e9fbcf09781c7c934b4910e94a50
Fixed in
  • 8d397582f6b5e9fbcf09781c7c934b4910e94a50
LinuxLinuxAffected
  • =5.8
Fixed in–

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]

References

Community reviews

Loading reviews…