# CVE-2026-80665: KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN

> A flaw in Linux kernel KVM arm64 nested virtualization allows a guest to trigger a host crash by causing a page fault that isn't properly handled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/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:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** BELL-CVE-2026-80665, DEBIAN-CVE-2026-80665, GHSA-qpmv-4rfj-75x9, UBUNTU-CVE-2026-80665

## What is CVE-2026-80665?

CVE-2026-80665 is a high-severity denial of service vulnerability in Linux, published on 28 Aug 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: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN

kvm_handle_vncr_abort() assumes that s1_walk_result conveys an abort
when kvm_translate_vncr() returns -EFAULT. This is not always the case
as it's possible to encounter 'late' failures on the output of S1
translation, e.g. a GFN outside of the memslots.

Fix it by preparing an external abort before returning from
kvm_translate_vncr(). Get rid of the BUG_ON() in the fault injection
path while at it.

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


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

Apply the vendor's patch.

## Is CVE-2026-80665 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80665 is a high-severity denial of service vulnerability in Linux, published on 28 Aug 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-80665 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-80665/ (Markdown: https://insights.sbomify.com/CVE-2026-80665/index.md)
```

## Sources

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

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