CVE-2026-3195: 
CBL Mariner vulnerability analysis and mitigation

CVE-2026-3195 is a heap-based buffer overflow vulnerability in QEMU's virtio-snd (virtual sound) device that can lead to arbitrary code execution on the host system. The flaw exists in the virtio_snd_pcm_in_cb function, which fails to verify whether the I/O vector (iov) can accommodate the incoming audio data buffer before writing, resulting in a heap out-of-bounds write. It affects QEMU versions 8.2.0 through 10.2.1 and is described as an incomplete fix for the previously disclosed CVE-2024-7730. The vulnerability was first reported on March 2, 2026, and publicly disclosed on June 19, 2026, with a CVSS v3.1 base score of 7.4 (High) (Github Advisory, Red Hat Bugzilla).

The root cause is classified as CWE-122 (Heap-based Buffer Overflow). In the virtio_snd_pcm_in_cb callback function responsible for reading audio input from the virtio-snd device, the code does not perform a bounds check to confirm that the iov (I/O vector) has sufficient capacity to hold the incoming PCM audio data buffer before writing to it. This missing validation allows a guest-controlled write operation to overflow the heap allocation. The vulnerability is a bypass/incomplete fix of CVE-2024-7730, meaning the original patch did not fully address all code paths where this condition could occur. Upstream fix commits are available at the QEMU GitLab repository (commits bcb53328aa70023f1405fade4e253e7f77567261 and 7994203bb1b83a6604f3ab00fe9598909bb66164) (Red Hat Bugzilla, Github Advisory).

Successful exploitation allows an unprivileged local user with access to a QEMU guest to write arbitrary data out of bounds on the host's heap, potentially enabling arbitrary code execution in the context of the QEMU host process. This represents a guest-to-host escape scenario with high confidentiality, integrity, and availability impact. In virtualized or cloud environments, this could allow a malicious tenant to compromise the hypervisor host and potentially affect other co-located virtual machines (Github Advisory, Red Hat Bugzilla).

No public proof-of-concept exploit code is known to exist, and there is no evidence of in-the-wild exploitation at this time (Github Advisory). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.112% (3rd percentile), indicating a low near-term probability of exploitation. Exploitation requires local access to a QEMU guest with the virtio-snd device enabled and involves high attack complexity, limiting the practical attack surface (Github Advisory).

Apply the upstream QEMU patches (commits bcb53328aa70023f1405fade4e253e7f77567261 and 7994203bb1b83a6604f3ab00fe9598909bb66164) which address the incomplete fix from CVE-2024-7730 (Red Hat Bugzilla). Distribution-specific updates are available: Ubuntu has released USN-8161-1, SUSE has released SUSE-SU-202621883-1 and SUSE-SU-20262386-1, and openSUSE has issued corresponding security announcements. As a workaround where patching is not immediately possible, disable the virtio-snd device in QEMU guest configurations if audio passthrough is not required, and restrict guest access to trusted users only.

Red Hat has classified this vulnerability as "Important" severity in their product security advisory and confirmed that their qemu-kvm packages across RHEL 6–10 and OpenShift Container Platform 4 are tracked, though listed as unaffected in current NVD data (Red Hat CSAF). The Yocto Project security mailing list also flagged the issue for embedded Linux maintainers. No significant social media controversy or notable researcher commentary beyond standard vulnerability tracking has been observed.