CVE-2026-89915
- Source
- https://cve.org/CVERecord?id=CVE-2026-89915
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89915.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-89915
- Downstream
- Published
- 2026-09-16T10:32:11Z
- Modified
- 2026-09-17T03:46:55Z
- Severity
-
- 9.3 (Critical) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H CVSS Calculator
- Summary
- KVM: arm64: Remove VM-wide VNCR mapping counter
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Remove VM-wide VNCR mapping counter
The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when a mapping is made in the fixmap, and decremented when unmapped.
As it turns out, this tracking has several flaws:
-
we are trying to invalidate TLBs, and the mapping is only an opportunistic consequence of the TLB. Checking this counter to decide whether a TLB needs to be invalidated may result in missed invalidations.
-
an L1 vcpu invalidating its own TLB (a very likely case) will not succeed in invalidating the VNCR pseudo TLB because that page is not mapped in L0 at this stage.
Given that this tracking fails at delivering the minimum guarantees that are required and is only a performance optimisation, remove it completely.
-
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89915.json" }- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/5453b85c7ebb605febac3df42021f9471663f051
- https://git.kernel.org/stable/c/87c2bbf189829dce4aaada8f82e3d54ccc037976
- https://git.kernel.org/stable/c/c55bc773b6e814406658fae7dc5c15f639ed816e
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89915.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-89915