GHSA-HCQ6-HVJH-VF66

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

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

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-89918"
  ],
  "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: 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": "GHSA-hcq6-hvjh-vf66",
  "modified": "2026-09-16T15:31:02Z",
  "published": "2026-09-16T12:30:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89918"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/34af2c3e31f91a739dc175459fdbd99ed952b457"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c624731ca6fe59ad8909ce4108301aa7560a91d6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ce447651a52ec077694172af10c4fffb11f56c43"
    }
  ],
  "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"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Loading…

Loading…

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.


Loading…