{
  "id": "CVE-2026-89929",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-89929",
  "published_at": "2026-09-16T10:32:20.855Z",
  "title": "KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU",
  "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: nVM: Ensure INVVPID is emulated on the correct physical CPU\n\nWhen emulating INVVPID, KVM executes INVVPID on the physical CPU using\nvpid02 (instead of the L1 assigned VPID), after doing some validations\non the operands. However, it is possible that the physical CPU KVM\nexecutes INVVPID on is different from the CPU L2 is running on.\n\nFor example, in the following scenario:\n- L2 runs on CPU #1 and exits to L1 (vmx-\u003enested.vmcs02.cpu=1)\n- L1 migrates to CPU #2 and executes INVVPID\n- KVM executes INVVPID on CPU #2\n- L1 migrates back to CPU #1 and runs L2 (vmx-\u003enested.vmcs02.cpu=1)\n\nThe TLB entries on CPU #1 are never invalidated, because INVVPID was\nexecuted on CPU #2, and vmcs02 never ran on a different pCPU (i.e.\nvmx_vcpu_load_vmcs() will *not* request KVM_REQ_TLB_FLUSH).\n\nEnsure that INVVPID is being executed on the same pCPU that L2 last ran\non, and if not, fallback to clearing last_vpid=0 to trigger a full VPID\nflush on the next nested VM-Enter (as KVM will detect L1 using a\ndifferent VPID for L2). If L2 ends up running on a different pCPU, KVM\nwill flush the TLB anyway through vmx_vcpu_load_vmcs().",
  "cvss_by_source": {
    "cna": 8.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 1759a565a25c814ced9281a708749c71fa69d6fe",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c d03e721801ac54b9fdf05668aa0c069f07913b68",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 27bdeb5fd19046ffba9ff234e92fe553eb2efb30",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 9941850e8adf164d005dbd3774c4b79e91a3cb8e",
          "\u003e= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, \u003c 6d00e67326d831e6e610933a3800712f4ffe6ec1"
        ],
        "fixed_in": [
          "1759a565a25c814ced9281a708749c71fa69d6fe",
          "d03e721801ac54b9fdf05668aa0c069f07913b68",
          "27bdeb5fd19046ffba9ff234e92fe553eb2efb30",
          "9941850e8adf164d005dbd3774c4b79e91a3cb8e",
          "6d00e67326d831e6e610933a3800712f4ffe6ec1"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "4.4"
        ],
        "fixed_in": [
          "0",
          "6.6.160",
          "6.12.110",
          "6.18.51",
          "7.2.5",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 1759a565a25c814ced9281a708749c71fa69d6fe or d03e721801ac54b9fdf05668aa0c069f07913b68 or 27bdeb5fd19046ffba9ff234e92fe553eb2efb30 or 9941850e8adf164d005dbd3774c4b79e91a3cb8e or 6d00e67326d831e6e610933a3800712f4ffe6ec1 or later.",
      "Upgrade Linux to 0 or 6.6.160 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
