dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2026-3195

HIGH · 7.4 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 →
79/100
Remediation priority · High
No privileges 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
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.

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 · high confidence

A heap out-of-bounds write vulnerability exists in QEMU's virtio-sound device emulation. The `virtio_snd_pcm_in_cb` function fails to validate that the iov (I/O vector) can accommodate the incoming audio data buffer before writing, allowing a malicious or crafted guest to overwrite adjacent heap memory. This flaw is an incomplete fix for the previous CVE-2024-7730.

MitigationUpdate QEMU to a version containing the complete bounds-checking fix for this vulnerability. If updates are unavailable, consider disabling the virtio-sound device in guest configurations or restricting QEMU's network exposure to minimize attack surface.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 QEMU installation and version
    Run 'qemu-system-x86_64 --version' or 'qemu-img --version' to determine the installed QEMU version. Compare this version against the version that contains the complete fix for CVE-2024-7730/CVE-2026-3195.
    Affected if The installed QEMU version is earlier than the version containing the complete fix for this vulnerability.
  2. Locate QEMU virtual machine configurations
    Search for QEMU VM configuration files in common locations such as /etc/qemu/, /var/lib/qemu/, ~/.config/qemu/, or within libvirt XML definitions if using libvirt. Look for XML or conf files that define virtual devices.
    Affected if A VM configuration file exists that defines or references a virtio-sound device.
  3. Check for active QEMU processes using virtio-sound
    Run 'ps aux | grep qemu' or 'pgrep -a qemu' to identify running QEMU processes. Inspect command-line arguments for '-device virtio-sound' or similar virtio-sound device definitions.
    Affected if A running QEMU process has the virtio-sound device enabled via command line or configuration.
  4. Verify virtio-sound device availability in QEMU
    Run 'qemu-system-x86_64 -device help | grep -i sound' or 'qemu-system-x86_64 -device virtio-sound-pci,help' to confirm the device is available in this QEMU build.
    Affected if The virtio-sound device is available in the QEMU binary and could be attached to a virtual machine.

A user is affected if they run a QEMU version prior to the fix with a virtio-sound device enabled in any virtual machine configuration, as the out-of-bounds write occurs when the device processes audio I/O without proper bounds validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update QEMU to a version containing the complete bounds-checking fix for this vulnerability. If updates are unavailable, consider disabling the virtio-sound device in guest configurations or restricting QEMU's network exposure to minimize attack surface.

Recommended fix Moderate confidence

Obtain the patched qemu-kvm version from Red Hat via RHSA/RHBA - consult security.access.redhat.com for the specific erratum

  1. Contact Red Hat for the specific errata/patch addressing CVE-2026-3195 for your installed version of qemu-kvm
  2. Alternatively, monitor Red Hat Security Advisory (RHSA) for CVE-2026-3195 updates
  3. Apply the vendor-supplied patch or update package via your system's package manager (e.g., `yum update qemu-kvm` or `dnf update qemu-kvm`)
  4. Reboot any running QEMU virtual machines or restart the libvirt service to ensure the updated QEMU binary is loaded
  5. Verify the installed qemu-kvm version includes the fix for CVE-2026-3195
Caveat Test virtual machine compatibility after QEMU upgrade in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3195 — 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-3195 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