CVE Tools

CVE-2026-93834

Qemu-kvm: 9pfs: use-after-free race in tlcreate/twalk allows vm guest escape

No known exploitation. No EPSS score yet. Only a workaround so far.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build is published yet. The vendor describes a workaround.

Steps

Written by AI from the record
  1. Check whether you run Red Hat virtual machines with shared folders enabled through QEMU/KVM 9pfs.
  2. Identify every affected Red Hat platform and restrict untrusted users from those guest systems while you assess exposure.
  3. No fixed version or vendor patch information is currently available; contact Red Hat for the supported remediation and deploy it when released.
  4. If you cannot patch yet, disable 9pfs shared folders or remove access to the affected virtual machines where practical.

What it is

From the CVE record

A use-after-free vulnerability was found in QEMU's 9pfs subsystem. A race condition between the main thread and a worker thread when processing concurrent Tlcreate and Twalk requests allows a malicious guest user to craft a fid path containing stale heap data, bypassing directory traversal restrictions and escaping the shared directory boundary. This can lead to arbitrary host file read/write and code execution (VM escape) as the QEMU process user.

In plain language

Written by AI from the record

This is a serious flaw in virtual-machine hosting on affected Red Hat platforms; small businesses should act if they run guest virtual machines using shared folders.

A guest user with access to QEMU/KVM 9pfs can trigger a use-after-free race between Tlcreate and Twalk requests, bypass shared-directory traversal restrictions, and potentially escape the VM as the QEMU process user.

If you're affected

  • Host file access
  • Host file modification
  • Virtual machine escape
  • Service disruption
  • Potential code execution

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

5 events over 0 days, from the signal feeds we watch.

  1. Workaround availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store