CVE-2026-74580 is a high-severity Linux kernel bug in vhost, the subsystem that accelerates I/O for virtual machines. It gives a local user a reliable path to root on the host, and in some VM setups it lets a guest write into host memory.
The CVE record has existed since August 21, 2026, but the full technical write-up, nicknamed "Vghost", only went public on October 12. It came with working exploit demos for both a local root escalation and a VM escape. The bug has been sitting in the kernel since Linux 4.11 back in 2017, which means a lot of fleets are carrying it right now.
For Cycle users: The fix is already in CycleOS for nodes using build v2026.09.24.1. Restart each server once to boot into the patched kernel, starting with hypervisor servers running virtual machines.
What is CVE-2026-74580?
CVE-2026-74580 is a memory corruption bug in the Linux kernel's vhost subsystem, rated 8.8 (High) by the kernel.org CNA. vhost is the piece of the kernel that speeds up networking and socket traffic for virtual machines, so it sits right on the boundary between a guest and its host.
The bug was discovered by Corvus AI and published by Tencent Zhuque Lab, who walked through it in a detailed write-up called "Vghost" on October 12. Their team confirmed working exploits on current releases of Ubuntu, RHEL, Amazon Linux, Azure Linux and Oracle Linux.
The risks break down into three buckets:
- Root on the host. A local, low-privileged user who can open a vhost device can escalate to root.
- VM escape. In certain configurations, a guest VM can write into the host's QEMU process and take control of it.
- Data exposure and crashes. Even short of full takeover, the bug can leak kernel memory, corrupt data or bring a host down.
Date | Milestone |
|---|---|
Oct 12, 2026 | Full "Vghost" write-up and exploit demos published |
Aug 25, 2026 | CVSS 8.8 score published by kernel.org CNA |
Aug 21, 2026 | CVE-2026-74580 announced by the Linux kernel CVE team |
Aug 3, 2026 | Fix lands in mainline |
Two major kernel vulnerabilities were announced earlier this year. Cycle acted quickly then as well, having a patch available for customers before the vulnerabilities were publicly announced.
Learn more
- Vghost: Beyond the Privilege Boundary (Tencent Zhuque Lab)
- CVE-2026-74580 record (cve.org)
Who's exposed
Every Linux kernel from 4.11 onward with vhost device IOTLB support is affected until patched. Fixed upstream stable releases start at 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9 and 7.2.
On Cycle, any server running virtual machines on a CycleOS build older than v2026.09.24.1 is vulnerable.
Can a VM break out?
The part of this disclosure that should get infrastructure teams' attention is what it means for virtual machines. vhost exists to serve VMs, and the researchers showed a guest can trigger the same bug from inside the VM.
In their demo, a process running inside a guest was able to reach out and take control of the host's virtualization process.
If you run on Cycle
The fix is in CycleOS starting with build v2026.09.24.1. Since kernel updates on CycleOS only take effect at reboot, any server that hasn't restarted since that build is still on the vulnerable kernel. Restart servers with the hypervisor feature first, then roll through the rest of the cluster one node at a time, and confirm each one reports v2026.09.24.1 or newer.