Host memory corruption via virtio-snd input overflow
Published Jun 19, 2026 · Updated Jun 19, 2026
Heap-based buffer overflow in QEMU 8.2.0 through 10.2.1 allows guest OS users to corrupt host-process memory through virtio-snd input. The virtio_snd_pcm_in_cb callback retains the status-header length in its capacity calculation and lets AUD_read exceed the remaining buffer space. A guest must configure and exercise virtio-snd input; corruption affects the QEMU host process, but no public exploit establishes code execution.
Summary
What happened
Heap-based buffer overflow in QEMU 8.2.0 through 10.2.1 allows guest OS users to corrupt host-process memory through virtio-snd input. The virtio_snd_pcm_in_cb callback retains the status-header length in its capacity calculation and lets AUD_read exceed the remaining buffer space. A guest must configure and exercise virtio-snd input; corruption affects the QEMU host process, but no public exploit establishes code execution.
The record
- CVE
- CVE-2026-3195
- Published
- Jun 19, 2026
- Updated
- Jun 19, 2026
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2026CVE publishedPublication date reported by the CVE source.
- Jun 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.2.0 <=10.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo