CVE-2026-23215

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

x86/vmware: Fix hypercall clobbers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/feb603a69f830acb58f78d604f0c29e63cd38f87
generic

x86/vmware: Fix hypercall clobbers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f467a92df61eb516a4ec36ee16234dd4e5ccf00
generic

x86/vmware: Fix hypercall clobbers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2687c848e57820651b9f69d30c4710f4219f7dbf

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.70—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1—

All Vendor Advisories

(9)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:50 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 23:57 UTCOSV refresh
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 43 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 09:49 UTCEG score recompute
  7. 2026-08-14 09:49 UTCVendor advisory
  8. 2026-08-14 09:49 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 02:07 UTCEG score recompute
  11. 2026-08-13 02:07 UTCVendor advisory
  12. 2026-08-13 02:07 UTCGHSA enrichment
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 07:30 UTCEG score recompute
  16. 2026-08-11 07:30 UTCVendor advisory
  17. 2026-08-11 07:30 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 14:09 UTCEG score recompute
  20. 2026-08-09 14:09 UTCVendor advisory
  21. 2026-08-09 14:09 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 21:41 UTCEG score recompute
  25. 2026-08-07 21:41 UTCVendor advisory
  26. 2026-08-07 21:41 UTCGHSA enrichment
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-06 03:35 UTCEG score recompute
  29. 2026-08-06 03:35 UTCVendor advisory
  30. 2026-08-06 03:35 UTCGHSA enrichment
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 10:38 UTCEPSS rescore
  34. 2026-08-03 10:35 UTCEPSS rescore
  35. 2026-08-02 20:21 UTCEG score recompute
  36. 2026-08-02 20:21 UTCVendor advisory
  37. 2026-08-02 20:21 UTCGHSA enrichment
  38. 2026-08-02 02:26 UTCEPSS rescore
  39. 2026-08-01 04:15 UTCEPSS rescore
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-27 14:13 UTCEPSS rescore
  42. 2026-07-27 13:28 UTCEG score recompute
  43. 2026-07-27 13:28 UTCGHSA enrichment

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-23215?
CVE-2026-23215 is a medium vulnerability published on February 18, 2026. 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…
When was CVE-2026-23215 disclosed?
CVE-2026-23215 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23215 actively exploited?
CVE-2026-23215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23215?
CVE-2026-23215 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23215

Explore →

Is Your Infrastructure Affected by CVE-2026-23215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs