CVE-2026-23215 (GCVE-0-2026-23215)

Vulnerability from cvelistv5 – Published: 2026-02-18 14:21 – Updated: 2026-05-11 22:02
VLAI
Title
x86/vmware: Fix hypercall clobbers
Summary
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.
Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 34bf25e820ae1ab38f9cd88834843ba76678a2fd , < 2f467a92df61eb516a4ec36ee16234dd4e5ccf00 (git)
Affected: 34bf25e820ae1ab38f9cd88834843ba76678a2fd , < feb603a69f830acb58f78d604f0c29e63cd38f87 (git)
Affected: 34bf25e820ae1ab38f9cd88834843ba76678a2fd , < 2687c848e57820651b9f69d30c4710f4219f7dbf (git)
Create a notification for this product.
Linux Linux Affected: 6.11
Unaffected: 0 , < 6.11 (semver)
Unaffected: 6.12.70 , ≤ 6.12.* (semver)
Unaffected: 6.18.10 , ≤ 6.18.* (semver)
Unaffected: 6.19 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/include/asm/vmware.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2f467a92df61eb516a4ec36ee16234dd4e5ccf00",
              "status": "affected",
              "version": "34bf25e820ae1ab38f9cd88834843ba76678a2fd",
              "versionType": "git"
            },
            {
              "lessThan": "feb603a69f830acb58f78d604f0c29e63cd38f87",
              "status": "affected",
              "version": "34bf25e820ae1ab38f9cd88834843ba76678a2fd",
              "versionType": "git"
            },
            {
              "lessThan": "2687c848e57820651b9f69d30c4710f4219f7dbf",
              "status": "affected",
              "version": "34bf25e820ae1ab38f9cd88834843ba76678a2fd",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/include/asm/vmware.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.11"
            },
            {
              "lessThan": "6.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.70",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.70",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.10",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19",
                  "versionStartIncluding": "6.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/vmware: Fix hypercall clobbers\n\nFedora QA reported the following panic:\n\n  BUG: unable to handle page fault for address: 0000000040003e54\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20251119-3.fc43 11/19/2025\n  RIP: 0010:vmware_hypercall4.constprop.0+0x52/0x90\n  ..\n  Call Trace:\n   vmmouse_report_events+0x13e/0x1b0\n   psmouse_handle_byte+0x15/0x60\n   ps2_interrupt+0x8a/0xd0\n   ...\n\nbecause the QEMU VMware mouse emulation is buggy, and clears the top 32\nbits of %rdi that the kernel kept a pointer in.\n\nThe QEMU vmmouse driver saves and restores the register state in a\n\"uint32_t data[6];\" and as a result restores the state with the high\nbits all cleared.\n\nRDI originally contained the value of a valid kernel stack address\n(0xff5eeb3240003e54).  After the vmware hypercall it now contains\n0x40003e54, and we get a page fault as a result when it is dereferenced.\n\nThe proper fix would be in QEMU, but this works around the issue in the\nkernel to keep old setups working, when old kernels had not happened to\nkeep any state in %rdi over the hypercall.\n\nIn theory this same issue exists for all the hypercalls in the vmmouse\ndriver; in practice it has only been seen with vmware_hypercall3() and\nvmware_hypercall4().  For now, just mark RDI/RSI as clobbered for those\ntwo calls.  This should have a minimal effect on code generation overall\nas it should be rare for the compiler to want to make RDI/RSI live\nacross hypercalls."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T22:02:32.925Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2f467a92df61eb516a4ec36ee16234dd4e5ccf00"
        },
        {
          "url": "https://git.kernel.org/stable/c/feb603a69f830acb58f78d604f0c29e63cd38f87"
        },
        {
          "url": "https://git.kernel.org/stable/c/2687c848e57820651b9f69d30c4710f4219f7dbf"
        }
      ],
      "title": "x86/vmware: Fix hypercall clobbers",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23215",
    "datePublished": "2026-02-18T14:21:52.515Z",
    "dateReserved": "2026-01-13T15:37:45.987Z",
    "dateUpdated": "2026-05-11T22:02:32.925Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-23215",
      "date": "2026-07-17",
      "epss": "0.00112",
      "percentile": "0.01658"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-23215\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-02-18T15:18:42.843\",\"lastModified\":\"2026-06-17T10:21:07.010\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/vmware: Fix hypercall clobbers\\n\\nFedora QA reported the following panic:\\n\\n  BUG: unable to handle page fault for address: 0000000040003e54\\n  #PF: supervisor write access in kernel mode\\n  #PF: error_code(0x0002) - not-present page\\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20251119-3.fc43 11/19/2025\\n  RIP: 0010:vmware_hypercall4.constprop.0+0x52/0x90\\n  ..\\n  Call Trace:\\n   vmmouse_report_events+0x13e/0x1b0\\n   psmouse_handle_byte+0x15/0x60\\n   ps2_interrupt+0x8a/0xd0\\n   ...\\n\\nbecause the QEMU VMware mouse emulation is buggy, and clears the top 32\\nbits of %rdi that the kernel kept a pointer in.\\n\\nThe QEMU vmmouse driver saves and restores the register state in a\\n\\\"uint32_t data[6];\\\" and as a result restores the state with the high\\nbits all cleared.\\n\\nRDI originally contained the value of a valid kernel stack address\\n(0xff5eeb3240003e54).  After the vmware hypercall it now contains\\n0x40003e54, and we get a page fault as a result when it is dereferenced.\\n\\nThe proper fix would be in QEMU, but this works around the issue in the\\nkernel to keep old setups working, when old kernels had not happened to\\nkeep any state in %rdi over the hypercall.\\n\\nIn theory this same issue exists for all the hypercalls in the vmmouse\\ndriver; in practice it has only been seen with vmware_hypercall3() and\\nvmware_hypercall4().  For now, just mark RDI/RSI as clobbered for those\\ntwo calls.  This should have a minimal effect on code generation overall\\nas it should be rare for the compiler to want to make RDI/RSI live\\nacross hypercalls.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\\n\\nx86/vmware: Soluci\u00f3n para las sobrescrituras de hiperllamadas\\n\\nFedora QA inform\u00f3 el siguiente p\u00e1nico:\\n\\n  BUG: unable to handle page fault for address: 0000000040003e54\\n  #PF: supervisor write access in kernel mode\\n  #PF: error_code(0x0002) - not-present page\\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20251119-3.fc43 11/19/2025\\n  RIP: 0010:vmware_hypercall4.constprop.0+0x52/0x90\\n  ..\\n  Call Trace:\\n   vmmouse_report_events+0x13e/0x1b0\\n   psmouse_handle_byte+0x15/0x60\\n   ps2_interrupt+0x8a/0xd0\\n   ...\\n\\nporque la emulaci\u00f3n de rat\u00f3n QEMU VMware tiene errores y borra los 32 bits superiores de %rdi donde el kernel manten\u00eda un puntero.\\n\\nEl controlador QEMU vmmouse guarda y restaura el estado del registro en un \u0027uint32_t data[6];\u0027 y, como resultado, restaura el estado con todos los bits altos borrados.\\n\\nRDI originalmente conten\u00eda el valor de una direcci\u00f3n de pila de kernel v\u00e1lida (0xff5eeb3240003e54). Despu\u00e9s de la hiperllamada de vmware, ahora contiene 0x40003e54, y obtenemos un fallo de p\u00e1gina como resultado cuando es desreferenciado.\\n\\nLa soluci\u00f3n adecuada estar\u00eda en QEMU, pero esto evita el problema en el kernel para mantener las configuraciones antiguas funcionando, cuando los kernels antiguos no hab\u00edan guardado ning\u00fan estado en %rdi durante la hiperllamada.\\n\\nEn teor\u00eda, este mismo problema existe para todas las hiperllamadas en el controlador vmmouse; en la pr\u00e1ctica, solo se ha visto con vmware_hypercall3() y vmware_hypercall4(). Por ahora, simplemente marca RDI/RSI como sobrescritos para esas dos llamadas. Esto deber\u00eda tener un efecto m\u00ednimo en la generaci\u00f3n de c\u00f3digo en general, ya que deber\u00eda ser raro que el compilador quiera mantener RDI/RSI activos a trav\u00e9s de hiperllamadas.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"arch/x86/include/asm/vmware.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"34bf25e820ae1ab38f9cd88834843ba76678a2fd\",\"lessThan\":\"2f467a92df61eb516a4ec36ee16234dd4e5ccf00\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"34bf25e820ae1ab38f9cd88834843ba76678a2fd\",\"lessThan\":\"feb603a69f830acb58f78d604f0c29e63cd38f87\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"34bf25e820ae1ab38f9cd88834843ba76678a2fd\",\"lessThan\":\"2687c848e57820651b9f69d30c4710f4219f7dbf\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"arch/x86/include/asm/vmware.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.11\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.11\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.70\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.10\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.19\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.11\",\"versionEndExcluding\":\"6.12.70\",\"matchCriteriaId\":\"4CF24CBE-557F-47D8-9FF4-305CAB4A0A36\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13\",\"versionEndExcluding\":\"6.18.10\",\"matchCriteriaId\":\"7156C23F-009E-4D05-838C-A2DA417B5B8D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"17B67AA7-40D6-4AFA-8459-F200F3D7CFD1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"C47E4CC9-C826-4FA9-B014-7FE3D9B318B2\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"F71D92C0-C023-48BD-B3B6-70B638EEE298\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"13580667-0A98-40CC-B29F-D12790B91BDB\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"CAD1FED7-CF48-47BF-AC7D-7B6FA3C065FC\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"3EF854A1-ABB1-4E93-BE9A-44569EC76C0D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*\",\"matchCriteriaId\":\"F5DC0CA6-F0AF-4DDF-A882-3DADB9A886A7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*\",\"matchCriteriaId\":\"EB5B7DFC-C36B-45D8-922C-877569FDDF43\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/2687c848e57820651b9f69d30c4710f4219f7dbf\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/2f467a92df61eb516a4ec36ee16234dd4e5ccf00\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/feb603a69f830acb58f78d604f0c29e63cd38f87\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-28T11:39:39+00:00",
      "cve": "CVE-2026-23215",
      "id": "CVE-2026-23215",
      "initial_release_date": "2026-02-18T00:00:00+00:00",
      "product_status:known_affected": "76",
      "product_status:known_not_affected": "198",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: x86/vmware: Fix hypercall clobbers",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23215.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.