{
  "id": "CVE-2026-89932",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-89932",
  "published_at": "2026-09-16T10:32:22.886Z",
  "title": "KVM: nVMX: Always flush vpid02 on first use",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 8.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nVMX: Always flush vpid02 on first use\n\nMake sure vpid02 is always flushed on first use by setting last_vpid=0\nwhen allocating vpid02.  nested_vmx_transition_tlb_flush() will always\ndetect a VPID change on first VM-Enter after VMXON, because VPID=0 in\nvmcs12 is not allowed if L1 enables VPID.\n\nThis avoids using stale TLB entries from a previous lifetime of the\nVPID, that might have been associated with a different vCPU (or a\ncompletely different VM).\n\nNote that last_vpid is already being initialized as 0 when the vCPU is\ncreated, but it is not reset when vpid02 is freed on VMXOFF. Hence, the\nproblem can only occur if L1 does VMXOFF -\u003e VMXON, runs an L2, and KVM\nhappens to reuse a VPID that has TLB entries on the physical CPU.",
  "cvss_by_source": {
    "cna": 8.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 8bc609999ec223089fec8d74c7de27d689606b36",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 62604376c313178811375f40a282fc2a46cd2311",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 8b98d662ab24f34710a56e03bc9169e4a5508606",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 22dfcc22c95e91295119a1c3b469816ce44c4804",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 121991d150735f3c0f7401678ce4d35c5b4ac898",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c f0772389413dce9657c7d6950abf3edbbd511356"
        ],
        "fixed_in": [
          "26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366",
          "8bc609999ec223089fec8d74c7de27d689606b36",
          "62604376c313178811375f40a282fc2a46cd2311",
          "8b98d662ab24f34710a56e03bc9169e4a5508606",
          "22dfcc22c95e91295119a1c3b469816ce44c4804",
          "121991d150735f3c0f7401678ce4d35c5b4ac898",
          "f0772389413dce9657c7d6950abf3edbbd511356"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "4.4"
        ],
        "fixed_in": [
          "0",
          "5.15.221",
          "6.1.188",
          "6.6.157",
          "6.12.110",
          "6.18.51",
          "7.2.5",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 or 8bc609999ec223089fec8d74c7de27d689606b36 or 62604376c313178811375f40a282fc2a46cd2311 or 8b98d662ab24f34710a56e03bc9169e4a5508606 or 22dfcc22c95e91295119a1c3b469816ce44c4804 or 121991d150735f3c0f7401678ce4d35c5b4ac898 or f0772389413dce9657c7d6950abf3edbbd511356 or later.",
      "Upgrade Linux to 0 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
