CVE-2026-23215: x86/vmware: Fix hypercall clobbers
Noroxi assessment
Priority: Monitor (action score 22/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 2687c848e57820651b9f69d30c4710f4219f7dbf, 2f467a92df61eb516a4ec36ee16234dd4e5ccf00, feb603a69f830acb58f78d604f0c29e63cd38f87.
Low priority for now. Upgrade to Linux Linux 2687c848e57820651b9f69d30c4710f4219f7dbf, 2f467a92df61eb516a4ec36ee16234dd4e5ccf00, feb603a69f830acb58f78d604f0c29e63cd38f87 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: x86/vmware: Fix hypercall clobbers Fedora QA reported the following panic: BUG: unable to handle page fault for address: 0000000040003e54 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20251119-3.fc43 11/19/2025 RIP: 0010:vmware_hypercall4.constprop.0+0x52/0x90 .. Call Trace: vmmouse_report_events+0x13e/0x1b0 psmouse_handle_byte+0x15/0x60 ps2_interrupt+0x8a/0xd0 ... because the QEMU VMware mouse emulation is buggy, and clears the top 32 bits of %rdi that the kernel kept a pointer in. The QEMU vmmouse driver saves and restores the register state in a "uint32_t data[6];" and as a result restores the state with the high bits all cleared. RDI originally contained the value of a valid kernel stack address (0xff5eeb3240003e54). After the vmware hypercall it now contains 0x40003e54, and we get a page fault as a result when it is dereferenced. The proper fix would be in QEMU, but this works around the issue in the kernel to keep old setups working, when old kernels had not happened to keep any state in %rdi over the hypercall. In theory this same issue exists for all the hypercalls in the vmmouse driver; in practice it has only been seen with vmware_hypercall3() and vmware_hypercall4(). For now, just mark RDI/RSI as clobbered for those two calls. This should have a minimal effect on code generation overall as it should be rare for the compiler to want to make RDI/RSI live across hypercalls.
- Published
- Feb 18, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- 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.
Is your version affected? Check itNoroxi 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 |
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.11affected
- 34bf25e820ae1ab38f9cd88834843ba76678a2fd and later · before 2f467a92df61eb516a4ec36ee16234dd4e5ccf00affected · git
- 34bf25e820ae1ab38f9cd88834843ba76678a2fd and later · before feb603a69f830acb58f78d604f0c29e63cd38f87affected · git
- 34bf25e820ae1ab38f9cd88834843ba76678a2fd and later · before 2687c848e57820651b9f69d30c4710f4219f7dbfaffected · git
- before 6.11not affected · semver
- 6.12.70 and later · up to and including 6.12.*not affected · semver
- 6.18.10 and later · up to and including 6.18.*not affected · semver
- 6.19 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.11 and later · before 6.12.70
- linux linux kernel6.13 and later · before 6.18.10
- linux linux kernel6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.10-1 | 6.18.10-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_11 | before 1-150700.1.3.1 | 1-150700.1.3.1 |
| SUSE:Linux Micro 6.2 | gdk-pixbuf | before 2.42.12-160000.4.1 | 2.42.12-160000.4.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-obs-build | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-syms | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
+3
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-23210Feb 14, 2026 · ice: Fix PTP NULL pointer dereference during VSI rebuild18Monitor
- ← EarlierCVE-2026-23211Feb 18, 2026 · mm, swap: restore swap_space attr aviod kernel panic22Monitor
- Later →CVE-2026-23218Feb 18, 2026 · gpio: loongson-64bit: Fix incorrect NULL check after devm_kcalloc()22Monitor
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 | 2687c848e57820651b9f69d30c4710f4219f7dbf | Vendor (CNA) |
| Linux Linux | 2f467a92df61eb516a4ec36ee16234dd4e5ccf00 | Vendor (CNA) |
| Linux Linux | feb603a69f830acb58f78d604f0c29e63cd38f87 | Vendor (CNA) |
| debian:linux | 6.12.73-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:gdk-pixbuf | 2.42.12-160000.4.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_11 | 1-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.28.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150700.7.37.2 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150700.7.37.2 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.28.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-syms-rt | 6.4.0-150700.7.37.1 · SUSE:Real Time Module 15 SP7 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.