Vulnerability-Lookup

GHSA-5P99-RG43-PX7F

Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31

Details

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry

A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario:

vcpu A walks the PTs to translate VNCR
before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issues a TLBI S1E2 for this VA
vcpu A inserts the TLB for something that is now invalid

This isn't a new problem, and we manage S2 by having the MMU notifier to bump up mmu_invalidate_seq on invalidation so that the fault can be replayed.

We can perform something similar here, and extend invalidate_vncr_va() to update the same counter, clearly indicating that the context has changed under our feet. This is safe as the invalidation always happen while holding the MMU lock for write, and that we sample the sequence number before walking S1.

Severity

9.3 (Critical)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-89916"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-16T11:17:00Z",
    "severity": "CRITICAL"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Make VNCR invalidation participate in MMU invalidation retry\n\nA VNCR TLB invalidation can occur on one vcpu while another vcpu is\nfaulting in this same page. Without correctly handling this, we can\nend up with the following scenario:\n\n- vcpu A walks the PTs to translate VNCR\n- before vcpu A is able to grab the MMU lock to insert the TLB,\n  vcpu B updates the S1 PTs with an invalid entry, and issues\n  a TLBI S1E2 for this VA\n- vcpu A inserts the TLB for something that is now invalid\n\nThis isn\u0027t a new problem, and we manage S2 by having the MMU notifier\nto bump up mmu_invalidate_seq on invalidation so that the fault can be\nreplayed.\n\nWe can perform something similar here, and extend invalidate_vncr_va() to\nupdate the same counter, clearly indicating that the context has\nchanged under our feet. This is safe as the invalidation always happen\nwhile holding the MMU lock for write, and that we sample the sequence\nnumber before walking S1.",
  "id": "GHSA-5p99-rg43-px7f",
  "modified": "2026-09-16T15:31:02Z",
  "published": "2026-09-16T12:30:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89916"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/11ee3faab4f1755d126bead9f882e75a7a677860"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2b7324f3a0c1072b9d578b8d42f199506753f26e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-89916 (GCVE-0-2026-89916)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:32 – Updated: 2026-09-16 14:40

Title

KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry

Summary

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario: - vcpu A walks the PTs to translate VNCR - before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issues a TLBI S1E2 for this VA - vcpu A inserts the TLB for something that is now invalid This isn't a new problem, and we manage S2 by having the MMU notifier to bump up mmu_invalidate_seq on invalidation so that the fault can be replayed. We can perform something similar here, and extend invalidate_vncr_va() to update the same counter, clearly indicating that the context has changed under our feet. This is safe as the invalidation always happen while holding the MMU lock for write, and that we sample the sequence number before walking S1.

Severity

9.3 (Critical)


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

Assigner

Linux mitre root

References

3 references

URL	Tags
https://git.kernel.org/stable/c/d8580e7aa189b0c6c…
https://git.kernel.org/stable/c/11ee3faab4f1755d1…
https://git.kernel.org/stable/c/2b7324f3a0c1072b9…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd (git) Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < 11ee3faab4f1755d126bead9f882e75a7a677860 (git) Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < 2b7324f3a0c1072b9d578b8d42f199506753f26e (git)
Linux	Linux	Affected: 6.16 Unaffected: 0 , < 6.16 (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/arm64/kvm/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd",
              "status": "affected",
              "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
              "versionType": "git"
            },
            {
              "lessThan": "11ee3faab4f1755d126bead9f882e75a7a677860",
              "status": "affected",
              "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
              "versionType": "git"
            },
            {
              "lessThan": "2b7324f3a0c1072b9d578b8d42f199506753f26e",
              "status": "affected",
              "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/kvm/nested.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "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.18.51",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc1",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Make VNCR invalidation participate in MMU invalidation retry\n\nA VNCR TLB invalidation can occur on one vcpu while another vcpu is\nfaulting in this same page. Without correctly handling this, we can\nend up with the following scenario:\n\n- vcpu A walks the PTs to translate VNCR\n- before vcpu A is able to grab the MMU lock to insert the TLB,\n  vcpu B updates the S1 PTs with an invalid entry, and issues\n  a TLBI S1E2 for this VA\n- vcpu A inserts the TLB for something that is now invalid\n\nThis isn\u0027t a new problem, and we manage S2 by having the MMU notifier\nto bump up mmu_invalidate_seq on invalidation so that the fault can be\nreplayed.\n\nWe can perform something similar here, and extend invalidate_vncr_va() to\nupdate the same counter, clearly indicating that the context has\nchanged under our feet. This is safe as the invalidation always happen\nwhile holding the MMU lock for write, and that we sample the sequence\nnumber before walking S1."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.3,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - An arm64 nested L1 hypervisor reaches the bug via KVM_RUN: a VNCR data abort (kvm_handle_vncr_abort \u2192 kvm_translate_vncr) races a trapped EL2 TLBI (handle_tlbi_el2 \u2192 kvm_handle_s1e2_tlbi \u2192 invalidate_vncr_va). This is local KVM ioctl/guest execution, not a network, adjacent-radio, or physical path.\nAC:L - The attacker owns both vCPUs of the same VM: one walks EL2 stage-1 for VNCR while another updates those S1 page tables and issues TLBI S1E2. A race the attacker drives on both sides is AC:L, and nested virt on NV-capable arm64 hosts is an attacker-selectable deployment.\nPR:N - Exploitation requires no host root or init-namespace capabilities beyond running hypervisor code in a tenant KVM guest on an arm64 host with nested virtualization enabled; the attacker operates entirely from within their assigned VM, consistent with other arm64 KVM nested-virt CVE scoring.\nUI:N - No victim user or administrator action is required beyond the attacker operating their own nested-virtualization workload; VNCR faults, S1 page-table updates, and TLBI S1E2 on a second vCPU are fully attacker-driven.\nS:C - The stale VNCR pseudo-TLB is installed in host KVM and mapped into the host per-CPU fixmap via __set_fixmap, so a guest-controlled walk/TLBI race corrupts host nested-MMU state and can retain a writable kernel mapping of a revoked PFN, crossing the guest-to-hypervisor security boundary.\nC:H - kvm_translate_vncr() stores a raw HPA and drops the page pin via kvm_release_faultin_page(). A walk that misses S1 TLBI retry still maps that HPA PAGE_KERNEL in the host VNCR fixmap, so NV2/sysreg emulation can read pages the guest has invalidated and the host may have reused, which is UAF-class disclosure.\nI:H - The same stale vncr_tlb is remapped writable (PAGE_KERNEL) in the host fixmap, so nested EL2 register writes and NV2 stores land in the old HPA after the guest\u0027s TLBI/BBM sequence. That is a host-kernel write to memory whose translation was revoked and may have been reused.\nA:H - Using a stale HPA through the host VNCR fixmap can oops or panic the host if the PFN was unmapped or recycled, and corrupting nested EL2 control state or reused host pages can hang or crash the hypervisor and co-resident VMs; the attacker can retrigger the walk/TLBI race."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-16T14:40:09.360Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd"
        },
        {
          "url": "https://git.kernel.org/stable/c/11ee3faab4f1755d126bead9f882e75a7a677860"
        },
        {
          "url": "https://git.kernel.org/stable/c/2b7324f3a0c1072b9d578b8d42f199506753f26e"
        }
      ],
      "title": "KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89916",
    "datePublished": "2026-09-16T10:32:11.967Z",
    "dateReserved": "2026-09-11T19:38:34.775Z",
    "dateUpdated": "2026-09-16T14:40:09.360Z",
    "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

GHSA-5P99-RG43-PX7F

CVE-2026-89916 (GCVE-0-2026-89916)

Tags

Sightings

Nomenclature

Related by attack behaviour