Skip to content
Infrastructure

CVE-2026-72277

9.3
Critical
EPSS 0.19%Patch availableAug 17, 2026

KVM (arm64) VNCR cache attribute bug can trigger SError, crashing VMs or host.

common questions

Is CVE-2026-72277 being exploited?

Not confirmed. CVE-2026-72277 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-72277?

CVE-2026-72277 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72277?

Yes. A fix has been recorded for CVE-2026-72277. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72277 affect?

CVE-2026-72277 affects Linux kernel KVM (arm64), arm64 virtualization hosts, Cloud providers using arm64 VMs, Edge/embedded devices with KVM on arm64. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72277?

Apply upstream Linux kernel KVM security updates for arm64 and reboot hosts/VMs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel KVM (arm64)arm64 virtualization hostsCloud providers using arm64 VMsEdge/embedded devices with KVM on arm64
impact

A guest can trigger SError via VNCR cache attributes, causing guest crash or host/VM instability (denial of service).

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and < d5436e18e4fc2886ac306304d884ea3b92e1edbf
  • affected>= 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and < bc00e0e376ee3572f5d26c174473abef1e35decc
  • affected>= 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and < 4bd7dbe0b2243e6aa735cae4d5e1ff988b30b2a6
  • affected6.16
vendor says fixed in< 6.16, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free