CVE-2026-68081: KVM: nVMX: Put vmcs12 pages if nested VM-Enter fails due to invalid guest state
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 2c87a087c20632d68920272173b5d7c47f9bcf70, 2f2312c422fd2695da772cecb30c69994b795964, 7996013b85687034d2e820cef94d6404192e3a3d; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2c87a087c20632d68920272173b5d7c47f9bcf70, 2f2312c422fd2695da772cecb30c69994b795964, 7996013b85687034d2e820cef94d6404192e3a3d; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 8, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.2affected
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before c174eb76484786721ae9a104344b952acf0e2717affected · git
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before a7bf4f5b19965e4466040ad6b24919c1ed326a84affected · git
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before f42669f931a6f45e5918cf5e99989b9a6c65e655affected · git
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before 7996013b85687034d2e820cef94d6404192e3a3daffected · git
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before 2c87a087c20632d68920272173b5d7c47f9bcf70affected · git
- 96c66e87deeeb3cc78a3b82a1de8e365eec206c1 and later · before 2f2312c422fd2695da772cecb30c69994b795964affected · git
- before 5.2not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.1.8-1.1 | 7.1.8-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64604Aug 6, 2026 · KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode0Monitor
- ← EarlierCVE-2026-68480Aug 6, 2026 · x86/bugs: Make Safe-RET robust against interrupt injection0Monitor
- Later →CVE-2026-68082Aug 8, 2026 · libceph: fix two unsafe bare decodes in decode_lockers()39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2c87a087c20632d68920272173b5d7c47f9bcf70 | Vendor (CNA) |
| Linux Linux | 2f2312c422fd2695da772cecb30c69994b795964 | Vendor (CNA) |
| Linux Linux | 7996013b85687034d2e820cef94d6404192e3a3d | Vendor (CNA) |
| Linux Linux | a7bf4f5b19965e4466040ad6b24919c1ed326a84 | Vendor (CNA) |
| Linux Linux | c174eb76484786721ae9a104344b952acf0e2717 | Vendor (CNA) |
| Linux Linux | f42669f931a6f45e5918cf5e99989b9a6c65e655 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.5-1 · Debian:14 | Package registry (OSV) |
| opensuse:kernel-source | 7.1.8-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0795 · Aug 10, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2f2312c422fd2695da772cecb30c69994b795964
- git.kernel.org/stable/c/7996013b85687034d2e820cef94d6404192e3a3d
- git.kernel.org/stable/c/a7bf4f5b19965e4466040ad6b24919c1ed326a84
- git.kernel.org/stable/c/c174eb76484786721ae9a104344b952acf0e2717
- git.kernel.org/stable/c/f42669f931a6f45e5918cf5e99989b9a6c65e655
Vendor advisories and official records. Exploit/PoC links are deliberately left out.