What is CVE-2026-3195?
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.
The record classifies CVE-2026-3195 under weakness class CWE-122. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 6 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 108 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.4 — HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 3.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-06-19
Is CVE-2026-3195 being exploited?
It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.
Affected products and versions
- Red Hat: Enterprise Linux 10, Enterprise Linux 6, Enterprise Linux 7, Enterprise Linux 8, Enterprise Linux 9, OpenShift Container Platform 4
How to fix CVE-2026-3195
No vendor patch reference has been recorded for CVE-2026-3195 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-3195
No threat campaign in the Threadlinqs corpus currently references CVE-2026-3195, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, GitHub Security Advisories. Last verified by Threadlinqs on .