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-68081KVM: nVMX: Put vmcs12 pages if nested VM-Enter fails due to invalid guest state

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Put vmcs12 pages if nested VM-Enter fails due to invalid guest state Put all vmcs12 pages if KVM synthesizes a nested VM-Exit due to invalid guest while emulating VMLAUNCH or VMRESUME. The invalid guest state path doesn't use nested_vmx_vmexit() as that API is intended to be used if and only if L2 is active, and the open coded equivalent neglects to put the vmcs12 pages. Failure to put the vmcs12 pages leaks any pinned pages (and/or mappings) if L1 retries VMLAUNCH/VMRESUME. Note, the !from_vmenter scenario doesn't suffer the same problem, as vmx_get_nested_state_pages() only gets/pins/maps the vmcs12 pages if L2 is active, i.e. if a "full" VM-Exit is guaranteed before KVM will retry getting vmcs12 pages.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 3 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < c174eb76484786721ae9a104344b952acf0e2717
    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < a7bf4f5b19965e4466040ad6b24919c1ed326a84
    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < f42669f931a6f45e5918cf5e99989b9a6c65e655
    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < 7996013b85687034d2e820cef94d6404192e3a3d
    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < 2c87a087c20632d68920272173b5d7c47f9bcf70
    • affected 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 – < 2f2312c422fd2695da772cecb30c69994b795964
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .