Vulnerability-Lookup

FKIE_CVE-2026-89929

Vulnerability from fkie_nvd - Published: 2026-09-16 11:17 - Updated: 2026-09-17 10:17

Severity

8.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Summary

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().

References

	URL	Tags
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/27bdeb5fd19046ffba9ff234e92fe553eb2efb30
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/6d00e67326d831e6e610933a3800712f4ffe6ec1
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/9941850e8adf164d005dbd3774c4b79e91a3cb8e
	416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/d03e721801ac54b9fdf05668aa0c069f07913b68

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/vmx/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d03e721801ac54b9fdf05668aa0c069f07913b68",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "27bdeb5fd19046ffba9ff234e92fe553eb2efb30",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "9941850e8adf164d005dbd3774c4b79e91a3cb8e",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "6d00e67326d831e6e610933a3800712f4ffe6ec1",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/vmx/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.4"
            },
            {
              "lessThan": "4.4",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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()."
    }
  ],
  "id": "CVE-2026-89929",
  "lastModified": "2026-09-17T10:17:04.940",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 8.8,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.0,
        "impactScore": 6.0,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-09-16T11:17:02.180",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/27bdeb5fd19046ffba9ff234e92fe553eb2efb30"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/6d00e67326d831e6e610933a3800712f4ffe6ec1"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/9941850e8adf164d005dbd3774c4b79e91a3cb8e"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d03e721801ac54b9fdf05668aa0c069f07913b68"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}

CVE-2026-89929 (GCVE-0-2026-89929)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:32 – Updated: 2026-09-17 09:29

Title

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

Summary

Severity

8.8 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Assigner

Linux mitre root

References

4 references

URL	Tags
https://git.kernel.org/stable/c/d03e721801ac54b9f…
https://git.kernel.org/stable/c/27bdeb5fd19046ffb…
https://git.kernel.org/stable/c/9941850e8adf164d0…
https://git.kernel.org/stable/c/6d00e67326d831e6e…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 , < d03e721801ac54b9fdf05668aa0c069f07913b68 (git) Affected: 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 , < 27bdeb5fd19046ffba9ff234e92fe553eb2efb30 (git) Affected: 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 , < 9941850e8adf164d005dbd3774c4b79e91a3cb8e (git) Affected: 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 , < 6d00e67326d831e6e610933a3800712f4ffe6ec1 (git)
Linux	Linux	Affected: 4.4 Unaffected: 0 , < 4.4 (semver) Unaffected: 6.12.110 , ≤ 6.12.* (semver) Unaffected: 6.18.51 , ≤ 6.18.* (semver) Unaffected: 7.2.5 , ≤ 7.2.* (semver) Unaffected: 7.3-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/vmx/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d03e721801ac54b9fdf05668aa0c069f07913b68",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "27bdeb5fd19046ffba9ff234e92fe553eb2efb30",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "9941850e8adf164d005dbd3774c4b79e91a3cb8e",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            },
            {
              "lessThan": "6d00e67326d831e6e610933a3800712f4ffe6ec1",
              "status": "affected",
              "version": "5c614b3583e7b6dab0c86356fa36c2bcbb8322a0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kvm/vmx/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.4"
            },
            {
              "lessThan": "4.4",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.110",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.51",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The bug is reached when an L1 nested VMX guest executes INVVPID, causing a VM-exit handled by handle_invvpid() on the host KVM_RUN ioctl path after VMXON/VMLAUNCH; no network, adjacent-radio, or physical path reaches this nVMX emulator.\nAC:L - A kvm-group or nested-virt tenant attacker controls both sides: pin the vCPU, run L2, migrate the vCPU thread with sched_setaffinity, execute INVVPID in L1, then migrate back so L2 resumes on the original pCPU with stale VPID translations; nested=1 and vpid=1 are defaults.\nPR:L - Exploitation needs /dev/kvm (kvm-group) or a cloud tenant VM with nested virtualization, plus CPL=0 in L1 after VMXON to execute INVVPID; KVM create/run ioctls have no CAP_SYS_ADMIN gate, and init-namespace host root is not required.\nUI:N - The attacker issues INVVPID from their own nested hypervisor and migrates the vCPU themselves; no separate victim action such as mounting a filesystem or opening a crafted file is required.\nS:C - Missed INVVPID leaves L2\u0027s VPID-tagged combined GVA-to-HPA TLB entries live on the pCPU where L2 last ran, so L2 can access host physical pages after L1 revoked those mappings, crossing the nested-guest versus L1-hypervisor and potentially guest-to-host isolation boundary.\nC:H - Stale combined mappings let L2 read host physical memory that L1 unmapped or reassigned to L1 or a sibling L2, and with page reuse those frames may hold other-guest or host data, yielding cross-VM information disclosure rather than a bounded leak.\nI:H - The retained TLB entries remain writable, so L2 can write through stale translations into remapped or recycled pages including L1 hypervisor memory, giving an arbitrary-write primitive consistent with missed-TLB and nested isolation-bypass scoring.\nA:H - Writes through stale VPID mappings into reused L1, sibling-guest, or host pages corrupt hypervisor or kernel state and can oops or panic the nested hypervisor or host, fully denying availability to co-resident VMs."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-17T09:29:17.783Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d03e721801ac54b9fdf05668aa0c069f07913b68"
        },
        {
          "url": "https://git.kernel.org/stable/c/27bdeb5fd19046ffba9ff234e92fe553eb2efb30"
        },
        {
          "url": "https://git.kernel.org/stable/c/9941850e8adf164d005dbd3774c4b79e91a3cb8e"
        },
        {
          "url": "https://git.kernel.org/stable/c/6d00e67326d831e6e610933a3800712f4ffe6ec1"
        }
      ],
      "title": "KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89929",
    "datePublished": "2026-09-16T10:32:20.855Z",
    "dateReserved": "2026-09-11T19:38:34.775Z",
    "dateUpdated": "2026-09-17T09:29:17.783Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

FKIE_CVE-2026-89929

CVE-2026-89929 (GCVE-0-2026-89929)

Tags

Sightings

Nomenclature

Related by attack behaviour