Linux kernel vuln in virtio/vsock can enable guest-controlled kernel memory corruption or guest-to-host escape; affects widespread virtualization deployments and risks host compromise.
CVE-2026-74614
Linux virtio/vsock race leads to use-after-free enabling kernel memory corruption.
Is CVE-2026-74614 being exploited?
Not confirmed. CVE-2026-74614 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-74614?
CVE-2026-74614 is rated High with a CVSS score of 8.4. 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-74614?
Yes. A fix has been recorded for CVE-2026-74614. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74614 affect?
CVE-2026-74614 affects Linux kernel (vsock/virtio), Virtual machines using virtio devices, Hosts/hypervisors handling virtio guests. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74614?
Apply vendor kernel updates ASAP and restart affected VMs/hosts; follow vendor advisories.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Guest-controlled use-after-free in virtio virtqueues enabling kernel memory corruption, crashes, local privilege escalation or guest-to-host escape.
Immediate action required
- affected>= 762c251c7f5c4ee5bef71460c6e822ed293fd69f and < 941329ce14c5f481223a10d1d4c8b57ea7f3048a
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < 29dd10583bf9d2744cd84b862e4257c0a5699570
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < a1fb0c5b8a7c2753758aeced40971f99449dde0c
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < eae099c764c7ebdb842eb1f638913e310bdd6513
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < bd43a7ec668be428265b3209eb43647aedcf720a
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < 1cecb4202afdbeddcf29d59baf596ac6ab753f7f
- affected>= bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c and < ebac8f6b1ef0e9278afe204b8692a7479988dace
- affected>= 5.15.138 and < 5.15.216
- affected5.19
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.