Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64562: KVM: nVMX: Hide shadow VMCS right after VMCLEAR

Noroxi assessment

Priority: Monitor (action score 35/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.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1dabef6e206568bf9d9ade74f6e56a48ea35695d, 4f50e6aec16f69627dbad5704d1e90a255d766a7, 589419470030a89f16cf19300658b6dc644ca946; azl3 kernel 6.6.145.2-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1dabef6e206568bf9d9ade74f6e56a48ea35695d, 4f50e6aec16f69627dbad5704d1e90a255d766a7, 589419470030a89f16cf19300658b6dc644ca946; azl3 kernel 6.6.145.2-1 on Azure Linux 3.0 6.6.150.1-1 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: Hide shadow VMCS right after VMCLEAR free_nested() frees the shadow VMCS while vmcs01 still points to it. But because it is asynchronous with respect to loaded_vmcs_clear(), the vCPU might migrate before the pointer is cleared and __loaded_vmcs_clear() may then execute VMCLEAR. The VMCS needs to stay attached until its explicit VMCLEAR completes, but then it can be hidden and the page safely freed.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Aug 4, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2026-64562

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 4.9affected
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before b82c3144d8264265448292ca406f60bafeba3b6faffected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before 4f50e6aec16f69627dbad5704d1e90a255d766a7affected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before dc3eecfa219ebc9d01eaf7d1abd1441efe884dabaffected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before af56298e9d86e6098cd1d2e155cb2949b7c45412affected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before 589419470030a89f16cf19300658b6dc644ca946affected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before 8001d2ce9d9bd09118ce523aef595aa094573ae3affected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before 1dabef6e206568bf9d9ade74f6e56a48ea35695daffected · git
    • 355f4fb1405ec29d0fac49b4d41fcd78cbd455d5 and later · before 622ebfac01ba4f9c0060cebd41257fe46fc4a0b3affected · git
    • before 4.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-4994Jul 30, 2026 · KVM: x86: wean fast IN from emulator_pio_in
    0Monitor
  • ← EarlierCVE-2026-64561Aug 4, 2026 · KVM: x86: Check for invalid/obsolete root *after* making MMU pages available
    35Monitor
  • Later →CVE-2026-64563Aug 4, 2026 · rhashtable: clear stale iter->p on table restart
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1dabef6e206568bf9d9ade74f6e56a48ea35695dVendor (CNA)
Linux Linux4f50e6aec16f69627dbad5704d1e90a255d766a7Vendor (CNA)
Linux Linux589419470030a89f16cf19300658b6dc644ca946Vendor (CNA)
Linux Linux622ebfac01ba4f9c0060cebd41257fe46fc4a0b3Vendor (CNA)
Linux Linux8001d2ce9d9bd09118ce523aef595aa094573ae3Vendor (CNA)
Linux Linuxaf56298e9d86e6098cd1d2e155cb2949b7c45412Vendor (CNA)
Linux Linuxb82c3144d8264265448292ca406f60bafeba3b6fVendor (CNA)
Linux Linuxdc3eecfa219ebc9d01eaf7d1abd1441efe884dabVendor (CNA)
azl3 kernel 6.6.145.2-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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.

Finders, 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.

  • CVE-2026-645640 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing
    39Monitor
  • CVE-2026-681276 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
    39Monitor
  • CVE-2026-681446 days apartphonet: pep: fix use-after-free in pep_get_sb()
    39Monitor
  • CVE-2026-681566 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
    39Monitor
  • CVE-2026-683816 days apartksmbd: pin conn during async oplock break notification
    39Monitor
  • CVE-2026-684266 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

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.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records