# CVE-2026-89914: KVM: arm64: Sign-extend VA for range-based TLBI invalidation

> Missing sign extension in KVM arm64 TLBI invalidation logic could lead to incorrect memory management behavior, requiring a kernel patch.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89914, DEBIAN-CVE-2026-89914, GHSA-qcff-3h48-22j7, UBUNTU-CVE-2026-89914

## What is CVE-2026-89914?

CVE-2026-89914 is a critical vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

KVM: arm64: Sign-extend VA for range-based TLBI invalidation

When the decode_range_tlbi() helper was moved to be used for S1 TLBIs,
the required sign extension was omitted. Add it.

As a result, special care must be taken to not overflow PA bits when
this is used for S2 invalidation.

## Which versions are affected by CVE-2026-89914?


## How do I fix CVE-2026-89914?

Apply the vendor's patch.

## Is CVE-2026-89914 being exploited?

There is no known exploitation of CVE-2026-89914 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89914 and fix it if it is affected.

What it is: CVE-2026-89914 is a critical vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89914 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89914/ (Markdown: https://insights.sbomify.com/CVE-2026-89914/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89914
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89914
- OSV: https://osv.dev/vulnerability/CVE-2026-89914

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89914/
Summaries are generated and may contain mistakes; the official description above is the record.