# CVE-2026-80699: KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context

> A flaw in Linux KVM arm64 nested virtualization on AmpereOne CPUs allows a guest to cause denial of service by triggering an interrupt handling errata.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80699, GHSA-4f2r-mgjf-292r, UBUNTU-CVE-2026-80699

## What is CVE-2026-80699?

CVE-2026-80699 is a 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: vgic: Avoid double-deactivate of IRQs in the nested context

In the nested state, the physical interrupt has already been
deactivated through the HW bit in the LR. The extra deactivation
would be harmless but can hit an errata case on AmpereOne, so
avoid it here.

On AmpereOne, deactivating a physical interrupt through
ICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not
active, but is the highest priority pending interrupt causes the
cpu to lose the interrupt pending state and also prevents the
delivery of future interrupts.

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


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

Apply the vendor's patch.

## Is CVE-2026-80699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80699 is a 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-80699 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-80699/ (Markdown: https://insights.sbomify.com/CVE-2026-80699/index.md)
```

## Sources

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

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