Linux vhost stale cache flaw CVE-2026-74580 grants root and enables VM escape to host
A stale cache bug in Linux vhost allows local users to gain root privileges or lets virtual machines break out to the host system.
Key points
- CVE-2026-74580, named Vghost, is a high-severity flaw in the Linux kernel vhost subsystem.
- Attackers can achieve arbitrary kernel read/write access and escalate to root on the host.
- In specific virtualization setups, untrusted guests can hijack the host's QEMU process.
The Vghost vulnerability (CVE-2026-74580) grants local users with access to vhost device nodes arbitrary read and write access to kernel memory, allowing them to escalate privileges to root. In virtualized environments using specific configurations, an untrusted guest can exploit this same flaw to write out of bounds into the host's QEMU process, potentially hijacking control flow or crashing the virtualization manager, according to The Hacker News.
How it unfolded
- Tencent Zhuque Lab researchers identified the flaw and released a fix on August 3.
- The team published a full technical write-up and working demonstrations on October 12.
- An official advisory was posted to the oss-security mailing list on October 13.
Who is affected
The vulnerability impacts Linux systems running the vhost subsystem, which accelerates input/output for virtual machines and containers. Local privilege escalation requires access to device nodes such as /dev/vhost-net or /dev/vhost-vsock. Researchers reproduced the attack on Ubuntu 26.04, RHEL 9.8, Amazon Linux 2023, Azure Linux 3.0, and Oracle Linux 10.2, noting that device permissions varied across these platforms, according to Cyber Security News.
The fix
Tencent Zhuque Lab released a patch for the vulnerability on August 3, before disclosing the details publicly. The flaw has been present in the kernel code for approximately nine years, dating back to changes introduced in Linux 4.11 in 2017, which added the metadata cache and deferred address validation. Updated Linux kernel releases now address the issue.
What made it possible
This incident stems from a stale metadata cache that fails to invalidate when virtual ring configurations change. Security teams usually monitor for caching mechanisms that bypass standard validation checks during state transitions. When a system updates resource mappings without clearing associated caches, it can lead to use-after-free or out-of-bounds access. Organizations should review how their virtualization stacks handle dynamic reconfiguration and ensure that cache invalidation logic aligns with all possible state changes to prevent unauthorized memory access.
What to do and how to stay safe: Linux
- Audit local user permissions for access to /dev/vhost-* device nodes and restrict them to necessary groups only.
- Verify that all Linux hosts are running updated kernel versions that include the Vghost patch.
- Review virtual machine configurations to ensure vIOMMU and iommu_platform settings are hardened.
- Monitor host processes for unexpected memory writes or control-flow hijacking attempts from guest systems.
Step-by-step guide: What Is Virtual Patching: How It Works Without Code Changes
General security guidance from the RedTeam Tribune newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-74580?
The vulnerability has a CVSS v3.1 score of 8.8, which is rated as high severity.
Has Vghost been exploited in the wild?
There is no public sign that the flaw has been exploited in the wild yet, according to The Hacker News.
Which Linux distributions were tested with the proof of concept?
Researchers tested the exploit on Ubuntu 26.04, RHEL 9.8, Amazon Linux 2023, Azure Linux 3.0, and Oracle Linux 10.2.
