CVE-2026-89929KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU
- 8.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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().
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 35 days later
· 35 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 1759a565a25c814ced9281a708749c71fa69d6fe
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < d03e721801ac54b9fdf05668aa0c069f07913b68
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 27bdeb5fd19046ffba9ff234e92fe553eb2efb30
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 9941850e8adf164d005dbd3774c4b79e91a3cb8e
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 6d00e67326d831e6e610933a3800712f4ffe6ec1
- affected 4.4
- unaffected < 4.4
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/1759a565a25c814ced9281a708749c71fa69d6fe (opens in a new tab)
- https://git.kernel.org/stable/c/d03e721801ac54b9fdf05668aa0c069f07913b68 (opens in a new tab)
- https://git.kernel.org/stable/c/27bdeb5fd19046ffba9ff234e92fe553eb2efb30 (opens in a new tab)
- https://git.kernel.org/stable/c/9941850e8adf164d005dbd3774c4b79e91a3cb8e (opens in a new tab)
- https://git.kernel.org/stable/c/6d00e67326d831e6e610933a3800712f4ffe6ec1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80529 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89929)Record last updated .