Linux kernel vhost-scsi affects virtualization hosts (widely deployed); can crash hypervisors and disrupt many VMs—enterprise-impacting.
CVE-2026-74702
Linux vhost-scsi bug allows guest-triggered host kernel crash causing hypervisor DoS
Is CVE-2026-74702 being exploited?
Not confirmed. CVE-2026-74702 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.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-74702?
CVE-2026-74702 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-74702?
Yes. A fix has been recorded for CVE-2026-74702. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74702 affect?
CVE-2026-74702 affects Linux kernel vhost-scsi (vhost_scsi module), KVM/QEMU virtualization hosts using vhost-scsi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74702?
Install kernel patch ASAP; reboot or reload vhost-scsi; avoid changing features while endpoint active.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A guest or actor can trigger a host kernel BUG_ON leading to host/hypervisor panic and denial of service, disrupting VMs and services.
Immediate action required
- affected>= bf2d650391be508dd8b5e188b65ed32300cf3489 and < a06e4611d45518896fbff4f45d9581578b107e91
- affected>= bf2d650391be508dd8b5e188b65ed32300cf3489 and < 9a3eb77a612f9d158e4d27df43677a014e9cfa55
- affected>= bf2d650391be508dd8b5e188b65ed32300cf3489 and < 42bc45df5905e2b7dccb72adaf7730f66cfbe03f
- affected6.15
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.