CVE-2026-72294
LoongArch Linux KVM ioctl lacks IRQ validation allowing invalid IRQ injection.
Is CVE-2026-72294 being exploited?
Not confirmed. CVE-2026-72294 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.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-72294?
CVE-2026-72294 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-72294?
Yes. A fix has been recorded for CVE-2026-72294. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72294 affect?
CVE-2026-72294 affects Linux kernel (LoongArch), KVM (kvm_vcpu_ioctl_interrupt), Hypervisors on LoongArch hosts, Guests with KVM ioctl access. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72294?
Install LoongArch kernel update for KVM and restrict KVM ioctl access to trusted users.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local userspace or a guest can invoke kvm_vcpu_ioctl_interrupt with invalid IRQs, causing host crash, KVM state corruption, or potential privilege escalation.
Patch when possible
- affected>= f45ad5b8aa9335bc6b30331b739e778f2f730b35 and < 15469ba0284c7cc01c38493391e9e73b918833c4
- affected>= f45ad5b8aa9335bc6b30331b739e778f2f730b35 and < efe27b19a15c384cad7c80de399f3107ab070e6d
- affected>= f45ad5b8aa9335bc6b30331b739e778f2f730b35 and < d4574547e04a47ad498149576f65b84475ea6f4c
- affected>= f45ad5b8aa9335bc6b30331b739e778f2f730b35 and < 09b318ab77b7a4fc9987fd98d1525fc55ddc2617
- affected6.7
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.