PoC Monitor
← All CVEs
CVE-2026-89929published 16 Sep 2026 10:32 UTCData: JSON · API

Linux

KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU

In the Linux kernel, the following vulnerability has been resolved: KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU When emulating INVVPID, KVM executes INVVPID on the physical CPU using vpid02 (instead of the L1 assigned VPID), after doing some validations on the operands. However, it is possible that the physical CPU KVM executes INVVPID on is different from the CPU L2 is running on. For example, in the following scenario: - L2 runs on CPU #1 and exits to L1 (vmx->nested.vmcs02.cpu=1) - L1 migrates to CPU #2 and executes INVVPID - KVM executes INVVPID on CPU #2 - L1 migrates back to CPU #1 and runs L2 (vmx->nested.vmcs02.cpu=1) The TLB entries on CPU #1 are never invalidated, because INVVPID was executed on CPU #2, and vmcs02 never ran on a different pCPU (i.e. vmx_vcpu_load_vmcs() will *not* request KVM_REQ_TLB_FLUSH). Ensure that INVVPID is being executed on the same pCPU that L2 last ran on, and if not, fallback to clearing last_vpid=0 to trigger a full VPID flush on the next nested VM-Enter (as KVM will detect L1 using a different VPID for L2). If L2 ends up running on a different pCPU, KVM will flush the TLB anyway through vmx_vcpu_load_vmcs().

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 1759a565a25c814ced9281a708749c71fa69d6fe
  • >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < d03e721801ac54b9fdf05668aa0c069f07913b68
  • >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 27bdeb5fd19046ffba9ff234e92fe553eb2efb30
  • >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 9941850e8adf164d005dbd3774c4b79e91a3cb8e
  • >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 6d00e67326d831e6e610933a3800712f4ffe6ec1

Fixed in 1759a565a25c814ced9281a708749c71fa69d6fe, d03e721801ac54b9fdf05668aa0c069f07913b68, 27bdeb5fd19046ffba9ff234e92fe553eb2efb30, 9941850e8adf164d005dbd3774c4b79e91a3cb8e, 6d00e67326d831e6e610933a3800712f4ffe6ec1

Linux Linux
  • 4.4

Fixed in 0, 6.6.160, 6.12.110, 6.18.51, 7.2.5, 7.3

Mitigation

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.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published16 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.