dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-3196

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An integer overflow vulnerability exists in the virtio-sound device's PCM_INFO request handling. A malicious guest can supply out-of-bounds stream counts that overflow integer calculations, causing unbounded memory allocation on the host and leading to denial of service.

MitigationApply vendor patches for the virtualization platform (typically QEMU/KVM) that implement proper bounds validation on stream counts in PCM_INFO requests, or restrict untrusted guests from having virtio-sound device access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if virtio-sound device is emulated
    Review VM configuration files or libvirt domain XML to locate any <sound> or virtio-sound device definitions, or run 'qemu-system-x86_64 -device virtio-sound-pci,help' to list available virtio-sound device options
    Affected if A virtio-sound device is attached to any VM
  2. Locate the QEMU or KVM hypervisor version
    Run 'qemu-system-x86_64 --version' or check the version of the qemu-kvm package installed on the host (e.g., 'rpm -q qemu-kvm' or 'dpkg -l qemu-system-x86')
    Affected if The installed QEMU/KVM version lacks the bounds validation patch for PCM_INFO stream count handling
  3. Verify guest trust level
    Review VM definitions to determine whether any VM with virtio-sound access is running untrusted or unpatched guest operating systems
    Affected if Untrusted or potentially malicious guests have direct access to the virtio-sound device

A system is affected if it runs a vulnerable QEMU/KVM version with a virtio-sound device attached to any VM, especially untrusted guests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for the virtualization platform (typically QEMU/KVM) that implement proper bounds validation on stream counts in PCM_INFO requests, or restrict untrusted guests from having virtio-sound device access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3196 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data