CVE-2023-1386

What it actually does

The 9p passthrough filesystem in QEMU fails to strip SUID and SGID bits when a guest user writes executable files, allowing those privilege bits to persist on the host filesystem backing the share.

Why it matters to the business

Attackers who already have a foothold inside a virtual machine can obtain elevated rights inside that guest and, in limited configurations, leverage the flaw to gain elevated rights on the hypervisor host, increasing the blast radius of a single compromised VM.

How an attack unfolds

A local attacker inside the guest writes a binary with SUID or SGID permissions through a 9p-mounted share; because the bits are not cleared, the file retains those permissions on the host side. The attacker then executes the binary inside the guest to obtain elevated privileges and, under rare shared-filesystem configurations, can abuse the same file to affect the host.

How to fix it

Upgrade QEMU to a release containing the corrected 9pfs implementation that properly drops SUID/SGID bits on writes. If an immediate update is not possible, disable or restrict 9pfs shares for untrusted guests and avoid exposing host directories that contain setuid binaries.

How to confirm the fix worked

Confirm the installed QEMU version is newer than the vulnerable releases, then create a test executable with SUID bits inside the guest via the 9p share and verify the bits are stripped on the host side.

Typical attack path

1. Obtain local access inside a QEMU guest that exposes a 9pfs share
2. Compile or copy an executable and set SUID/SGID mode bits while writing it via the 9p mount
3. Execute the resulting binary inside the guest to gain elevated privileges
4. Abuse the retained permissions on the host-side backing file to escalate on the hypervisor (rare)

How to detect it

Search guest and host audit logs for creation or chmod operations on files with SUID/SGID bits inside 9p-mounted directories; monitor for unexpected setuid binaries appearing in shared host paths.

What your security team should do

• Apply the QEMU security update as soon as packages are available in your distribution
• Audit all VMs that use 9pfs shares and restrict the feature to trusted workloads only
• Enable file-integrity monitoring on host directories exposed via 9pfs to detect unexpected SUID/SGID files