Skip to content
Systems

CVE-2026-72283

8.8
High
EPSS 0.18%Patch availableAug 17, 2026

KVM irqfd/IRTE use-after-free allows guest-triggered host kernel compromise.

common questions

Is CVE-2026-72283 being exploited?

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

How severe is CVE-2026-72283?

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

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

What does CVE-2026-72283 affect?

CVE-2026-72283 affects Linux kernel (KVM/x86), KVM hosts, VFIO PCI devices/drivers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72283?

Install vendor kernel updates; patch VFIO/hypervisor components; isolate untrusted 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/x86)KVM hostsVFIO PCI devices/drivers
impact

Guest or local attacker can trigger a host-kernel use-after-free, enabling memory corruption, privilege escalation, or guest→host escape.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 77e1b8332d1d7aa786f7515e9bd4055def6a1e06 and < d1379888cc4230bac647ec24ab83306afbd03e88
  • affected>= 77e1b8332d1d7aa786f7515e9bd4055def6a1e06 and < d5560b6569cd05ba72c6b33427fbabc6ec46b8cf
  • affected>= 77e1b8332d1d7aa786f7515e9bd4055def6a1e06 and < ed446e8aa894883c08892cfee69782fdf8f6c3ca
  • affected6.17
vendor says fixed in< 6.17, >= 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