# CVE-2026-3195: Qemu-kvm: virtio-snd: heap buffer overflow in virtio_snd_pcm_in_cb (incomplete fix for cve-2024-7730)

> Heap buffer overflow in QEMU virtio-snd allows guest-to-host code execution or privilege escalation via audio input.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-91269, BELL-CVE-2026-3195, DEBIAN-CVE-2026-3195, GHSA-x3gf-fc58-4mvj, UBUNTU-CVE-2026-3195

## What is CVE-2026-3195?

CVE-2026-3195 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 19 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in QEMU. When reading input audio in the virtio-snd device input callback, the `virtio_snd_pcm_in_cb` function did not check whether the iov could fit the data buffer, potentially leading to a heap out-of-bounds write. This issue exists due to an incomplete fix for CVE-2024-7730.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-3195?


## How do I fix CVE-2026-3195?

Apply the vendor's patch.

## Is CVE-2026-3195 being exploited?

There is no known exploitation of CVE-2026-3195 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3195 and fix it if it is affected.

What it is: CVE-2026-3195 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 19 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3195 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3195/ (Markdown: https://insights.sbomify.com/CVE-2026-3195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3195
- OSV: https://osv.dev/vulnerability/CVE-2026-3195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3195/
Summaries are generated and may contain mistakes; the official description above is the record.