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

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.

Published: 2026-06-19 Last update: 2026-06-22 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-3195 is rated Low Risk (30.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.11%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-3195

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-23 0.11%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-3195

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.4 5.9 [email protected]

Weakness enumeration for CVE-2026-3195

GitHub Security Advisory for CVE-2026-3195

GHSA-x3gf-fc58-4mvj · Severity: high — A flaw was found in QEMU. When reading input audio in the virtio-snd device input callback, the ...

OS Trackers for CVE-2026-3195

vendor priority summary link
debian unimportant CVE-2026-3195 unimportant priority: Debian including 1 source packages (qemu), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-3195
redhat high https://access.redhat.com/security/cve/CVE-2026-3195
suse high CVE-2026-3195 severity important: SUSE including 49 source package names (qemu, qemu-SLOF, …), 481 product×package rows across 20 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (20 product lines)): Known Not Affected 481. https://www.suse.com/security/cve/CVE-2026-3195/
ubuntu medium CVE-2026-3195 medium priority: Ubuntu including 1 source packages (qemu), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 4, released 3, not-affected 1. https://ubuntu.com/security/CVE-2026-3195

Affected software / configurations for CVE-2026-3195

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-3195

cvelogic Threat Intelligence