Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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]

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46059, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < 98717fb482fa269db491f7c84aec777d3aeb2cd1
    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < b1a45e8a59bcf1f1ec0da6d4e42190b4211c67fc
    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < f9197a9dd1408e203147326139122f9c5312ce9c
    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < 3428ed1529a1af4cce5aff6c5bd2fcc39ad726bb
    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < 69fe1411a5ce678b4da6489b5d2282b4e1d13acf
    • affected cc440cdad5b7a4c1de12dace725209eb3e0cf663 – < 8d397582f6b5e9fbcf09781c7c934b4910e94a50
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46059 badge
[![CVE-2026-46059](https://cveledger.app/badge/CVE-2026-46059.svg)](https://cveledger.app/cve/CVE-2026-46059)

Record last updated .