Menu

Star on GitHub · 3.2k

CVE-2026-80699

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…

Published Aug 28, 2026EPSS 0.20%

Overview

CVE-2026-80699 is a known-severity vulnerability. It was published on August 28, 2026.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80699?

CVE-2026-80699 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-80699?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80699?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80699?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80699 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.