CVE-2026-89918 (GCVE-0-2026-89918)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:32 – Updated: 2026-10-19 08:54
VLAI
Title
KVM: arm64: Correctly handle end of VA space TLBI invalidation
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start and a size. However, the way the comparison is done doesn't account for address rollover, as it compares an address with (base + size). This works nicely until this expression represent the last page/block in the TTBR1 VA space, as the result is a big fat 0. And a failed TLB invalidation. Rewrite the comparison in a way that is immune to the address rollover (making the end address inclusive instead of exclusive), and move this into a common helper that is used by both VA and IPA invalidations, as suggested by Hyunwoo Kim (although the IPA version didn't suffer from this particular problem, obviously).
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 CNA under the mitre root
CNA scorecard D 53/100 over 6637 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < ce447651a52ec077694172af10c4fffb11f56c43 (git)
Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < c624731ca6fe59ad8909ce4108301aa7560a91d6 (git)
Affected: 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 , < 34af2c3e31f91a739dc175459fdbd99ed952b457 (git)
guessed Create a notification for this product.
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 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
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": "ce447651a52ec077694172af10c4fffb11f56c43",
              "status": "affected",
              "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
              "versionType": "git"
            },
            {
              "lessThan": "c624731ca6fe59ad8909ce4108301aa7560a91d6",
              "status": "affected",
              "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
              "versionType": "git"
            },
            {
              "lessThan": "34af2c3e31f91a739dc175459fdbd99ed952b457",
              "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",
              "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",
                  "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: Correctly handle end of VA space TLBI invalidation\n\nOur TLB invalidation by VA code is based on comparing two ranges,\none defined by the TLB, and one defined by the TLBI instruction.\n\nEach range is defined by a start and a size. However, the way the\ncomparison is done doesn\u0027t account for address rollover, as it\ncompares an address with (base + size). This works nicely until\nthis expression represent the last page/block in the TTBR1 VA space,\nas the result is a big fat 0. And a failed TLB invalidation.\n\nRewrite the comparison in a way that is immune to the address\nrollover (making the end address inclusive instead of exclusive),\nand move this into a common helper that is used by both VA and IPA\ninvalidations, as suggested by Hyunwoo Kim (although the IPA version\ndidn\u0027t suffer from this particular problem, obviously)."
        }
      ],
      "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 - The bug is reached when an arm64 nested-KVM L1 hypervisor executes EL2/EL1 TLBI-by-VA instructions that trap into KVM_RUN and run handle_tlbi_el2()/handle_tlbi_el1() \u2192 kvm_handle_s1e2_tlbi() \u2192 invalidate_vncr_va(); no network, adjacent-radio, or physical-device path reaches this VNCR pseudo-TLB comparison.\nAC:L - An attacker controlling an L1 nested hypervisor can place VNCR_EL2 on the last TTBR1 page or issue a VA-scoped TLBI for that range so base+size wraps to 0, causing a deterministic missed invalidation; nested virt on arm64 cloud hosts is an attacker-selectable deployment, not an uncontrollable condition.\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 placement, stage-1 remaps, and TLBI-by-VA issuance are fully attacker-driven from within the guest.\nS:C - Failed VNCR pseudo-TLB invalidation leaves the host kernel\u0027s per-CPU fixmap aliasing a stale guest physical page for nested EL2 register state, so the hypervisor reads and writes the wrong memory after the guest remaps that VA, crossing the guest-to-hypervisor security boundary.\nC:H - A missed invalidation keeps a host PAGE_KERNEL fixmap to the old HPA after the L1 remaps VNCR_EL2, so KVM continues to read nested EL2 register state from a guest page that should no longer back VNCR, disclosing hypervisor-viewed contents across the stale translation.\nI:H - The same stale writable fixmap lets the host write nested EL2 register values into a guest page the L1 has already remapped or reused, and lets the guest inject attacker-controlled EL2 sysreg contents through the old page while KVM trusts it as VNCR, corrupting hypervisor-emulated nested state.\nA:H - Stale VNCR translations leave host KVM and FEAT_NV2 hardware using inconsistent nested EL2 state and the wrong guest page, which can crash or livelock the host nested-virt paths and deny service to co-resident VMs on the hypervisor."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:54:52.658Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ce447651a52ec077694172af10c4fffb11f56c43"
        },
        {
          "url": "https://git.kernel.org/stable/c/c624731ca6fe59ad8909ce4108301aa7560a91d6"
        },
        {
          "url": "https://git.kernel.org/stable/c/34af2c3e31f91a739dc175459fdbd99ed952b457"
        }
      ],
      "title": "KVM: arm64: Correctly handle end of VA space TLBI invalidation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89918",
    "datePublished": "2026-09-16T10:32:13.304Z",
    "dateReserved": "2026-09-11T19:38:34.775Z",
    "dateUpdated": "2026-10-19T08:54:52.658Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-89918",
      "date": "2026-11-04",
      "epss": "0.00194",
      "percentile": "0.09159"
    },
    "microsoft_vex": {
      "current_release_date": "2026-10-21T18:43:14.000Z",
      "cve": "CVE-2026-89918",
      "id": "msrc_CVE-2026-89918",
      "initial_release_date": "2026-10-20T22:22:30.000Z",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "KVM: arm64: Correctly handle end of VA space TLBI invalidation",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-89918.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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": "ce447651a52ec077694172af10c4fffb11f56c43",
                    "status": "affected",
                    "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "c624731ca6fe59ad8909ce4108301aa7560a91d6",
                    "status": "affected",
                    "version": "4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "34af2c3e31f91a739dc175459fdbd99ed952b457",
                    "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",
                    "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: arm64: Correctly handle end of VA space TLBI invalidation\n\nOur TLB invalidation by VA code is based on comparing two ranges,\none defined by the TLB, and one defined by the TLBI instruction.\n\nEach range is defined by a start and a size. However, the way the\ncomparison is done doesn\u0027t account for address rollover, as it\ncompares an address with (base + size). This works nicely until\nthis expression represent the last page/block in the TTBR1 VA space,\nas the result is a big fat 0. And a failed TLB invalidation.\n\nRewrite the comparison in a way that is immune to the address\nrollover (making the end address inclusive instead of exclusive),\nand move this into a common helper that is used by both VA and IPA\ninvalidations, as suggested by Hyunwoo Kim (although the IPA version\ndidn\u0027t suffer from this particular problem, obviously)."
          }
        ],
        "id": "CVE-2026-89918",
        "lastModified": "2026-10-19T09:18:37.293",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 9.3,
                "baseSeverity": "CRITICAL",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.5,
              "impactScore": 6.0,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-09-16T11:17:00.867",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/34af2c3e31f91a739dc175459fdbd99ed952b457"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/c624731ca6fe59ad8909ce4108301aa7560a91d6"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/ce447651a52ec077694172af10c4fffb11f56c43"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-04T15:58:58+00:00",
      "cve": "CVE-2026-89918",
      "id": "CVE-2026-89918",
      "initial_release_date": "2026-09-16T00:00:00+00:00",
      "product_status:known_affected": "77",
      "product_status:known_not_affected": "202",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: KVM: arm64: Correctly handle end of VA space TLBI invalidation",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89918.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "low",
      "current_release_date": "2026-10-20T00:55:06Z",
      "cve": "CVE-2026-89918",
      "id": "CVE-2026-89918",
      "initial_release_date": "2026-09-17T16:34:56Z",
      "product_status:known_affected": "0",
      "product_status:known_not_affected": "348",
      "product_status:recommended": "4",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-89918",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-89918.json",
      "version": "5"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.