# CVE-2026-3196: Qemu-kvm: virtio-snd: integer overflow leading to unbounded memory allocation

> A malicious guest can trigger an integer overflow in QEMU's virtio-snd device, causing unbounded memory allocation and host denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** AZL-91272, BELL-CVE-2026-3196, DEBIAN-CVE-2026-3196, GHSA-crqh-2v7r-3m9w, UBUNTU-CVE-2026-3196

## What is CVE-2026-3196?

CVE-2026-3196 is a medium-severity 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

An integer overflow vulnerability was found in the virtio-snd device via PCM_INFO requests from the guest. A malicious guest can provide out-of-bounds stream counts, potentially leading to unbounded memory allocation on the host and a denial of service condition.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-3196 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3196 is a medium-severity 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-3196 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-3196/ (Markdown: https://insights.sbomify.com/CVE-2026-3196/index.md)
```

## Sources

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

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