CVE-2026-64284: KVM: x86: Ensure vendor's exit handler runs before fastpath userspace exits
Noroxi assessment
Priority: Monitor (action score 28/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.13% (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 0ffedf43910e44b76c2c1db4e9fbf12b268190c1, 4ad73ef0e7966ecfe67de0060537b4cb14d9acd4, b3436d9b9b1affe1c3191ac9831308923f5f03c3.
Low priority for now. Upgrade to Linux Linux 0ffedf43910e44b76c2c1db4e9fbf12b268190c1, 4ad73ef0e7966ecfe67de0060537b4cb14d9acd4, b3436d9b9b1affe1c3191ac9831308923f5f03c3 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: x86: Ensure vendor's exit handler runs before fastpath userspace exits Move the handling of fastpath userspace exits into vendor code to ensure KVM runs vendor specific operations that need to run before userspace gains control of the vCPU. E.g. for VMX (and soon to be for SVM as well), KVM needs to flush the PML buffer prior to exiting to userspace, otherwise any memory written by the final KVM_RUN might never be flagged as dirty. Note, waiting to snapshot CR0 and CR3 until svm_handle_exit() is flawed in general, as that risks consuming stale state in a fastpath handler. That will be addressed in a future change.
- Published
- Jul 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-367
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- 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.
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
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
- 6.12affected
- f7f39c50edb9d336274371953275e0d3503b9b75 and later · before b3436d9b9b1affe1c3191ac9831308923f5f03c3affected · git
- f7f39c50edb9d336274371953275e0d3503b9b75 and later · before 4ad73ef0e7966ecfe67de0060537b4cb14d9acd4affected · git
- f7f39c50edb9d336274371953275e0d3503b9b75 and later · before f2ca2b5326211bd38490f0497eb583721ce0bbc0affected · git
- f7f39c50edb9d336274371953275e0d3503b9b75 and later · before 0ffedf43910e44b76c2c1db4e9fbf12b268190c1affected · git
- before 6.12not affected · semver
- 6.12.96 and later · up to and including 6.12.*not affected · semver
- 6.18.39 and later · up to and including 6.18.*not affected · semver
- 7.1.4 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
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-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64279Jul 25, 2026 · i2c: core: fix adapter deregistration race31Monitor
- ← EarlierCVE-2026-64283Jul 25, 2026 · KVM: guest_memfd: Treat memslot binding offset+size as unsigned values28Monitor
- Later →CVE-2026-64286Jul 25, 2026 · KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU32Monitor
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 | 0ffedf43910e44b76c2c1db4e9fbf12b268190c1 | Vendor (CNA) |
| Linux Linux | 4ad73ef0e7966ecfe67de0060537b4cb14d9acd4 | Vendor (CNA) |
| Linux Linux | b3436d9b9b1affe1c3191ac9831308923f5f03c3 | Vendor (CNA) |
| Linux Linux | f2ca2b5326211bd38490f0497eb583721ce0bbc0 | Vendor (CNA) |
| debian:linux | 6.12.96-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | 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.
- CVE-2025-38352368 days apartposix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV61This week
- CVE-2026-640916 days apartbatman-adv: tt: fix TOCTOU race for reported vlans39Monitor
- CVE-2026-640346 days apartnet: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer37Monitor
- CVE-2026-639376 days apartKVM: SEV: Use READ_ONCE() when reading entries/indices from PSC buffer35Monitor
- CVE-2026-638676 days apartmptcp: close TOCTOU race while computing rcv_wnd32Monitor
- CVE-2026-641126 days apartrbd: eliminate a race in lock_dwork draining on unmap31Monitor
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).
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
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.