CVE-2026-68081: Linux kernel · KVM: nVMX: Put vmcs12 pages if nested VM-Enter fails due to invalid guest state
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f42669f931a6f45e5918cf5e99989b9a6c65e655 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f42669f931a6f45e5918cf5e99989b9a6c65e655, a7bf4f5b19965e4466040ad6b24919c1ed326a84, 7996013b85687034d2e820cef94d6404192e3a3d +2
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/a7bf4f5b19965e4466040ad6b24919c1ed326a84 (opens in a new tab)
- git.kernel.org/stable/c/f42669f931a6f45e5918cf5e99989b9a6c65e655 (opens in a new tab)
- git.kernel.org/stable/c/7996013b85687034d2e820cef94d6404192e3a3d (opens in a new tab)
- git.kernel.org/stable/c/2c87a087c20632d68920272173b5d7c47f9bcf70 (opens in a new tab)
- git.kernel.org/stable/c/2f2312c422fd2695da772cecb30c69994b795964 (opens in a new tab)