Skip to content
Infrastructure

CVE-2026-74516

8.2
High
EPSS 0.14%Patch availableAug 17, 2026

KVM SVM bug lets nested guest send interrupts/read host APIC, causing host DoS.

common questions

Is CVE-2026-74516 being exploited?

Not confirmed. CVE-2026-74516 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.14% probability of exploitation in the next 30 days.

How severe is CVE-2026-74516?

CVE-2026-74516 is rated High with a CVSS score of 8.2. 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-74516?

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

What does CVE-2026-74516 affect?

CVE-2026-74516 affects Linux kernel (kvm, kvm_amd/svm), KVM hosts on AMD SVM, Nested virtualization (L1/L2) setups, KVM-based cloud hypervisors. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74516?

Apply vendor kernel/KVM patches, disable or restrict nested virtualization until patched.

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

executive summary
technical analysis
affected
Linux kernel (kvm, kvm_amd/svm)KVM hosts on AMD SVMNested virtualization (L1/L2) setupsKVM-based cloud hypervisors
impact

An L1 nested guest can read host APIC state, send arbitrary interrupts, alter priorities and trivially DoS the host.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < 4ca05385b3ddbd463be17c6d69ec76fca657081d
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < 6664a5aea45318f4ec156a729949b474dd6e3159
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < f12373625b4dc9bcc89c41872648878c73bb9272
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < 7668c58dcf465559dc7a0d2e95e9cb79cf47454b
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < 89f9e8398e79c49886766fc24a84c37726231104
  • affected>= 091abbf578f926e763adc0f577baeb7f405b4bdc and < 7d3aae206663c4e006b25a1c7a20a4029e67da76
  • affected6.0
vendor says fixed in< 6.0, >= 6.1.183 and <= 6.1.*, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 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