Vulnerability in QEMU (CVE-2026-3195)
Summary
Vulnerability in QEMU (CVE-2026-3195). Successful exploitation can lead to full system takeover. Exploitable via virtio_snd_pcm_in_cb.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3195 has been found in QEMU.
Attackers can target a specific entry point like virtio_snd_pcm_in_cb over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "QEMU CVE-2026-3195" on the vendor's site.
CVE-2026-3195 (QEMU) — CWE-122 / CVSS v3 7.4
Attack vector: local / unauthenticated / no user interaction
Attack surface: virtio_snd_pcm_in_cb
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-122) exists in QEMU. Attackers reach the vulnerable code path via virtio_snd_pcm_in_cb without authentication.
Check the vendor advisory for the affected versions of QEMU. Attack surface: virtio_snd_pcm_in_cb.
Severity: High (CVSS 7.4/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'QEMU' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'QEMU' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
QEMUを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-3195 qemu Fixed in: 9.0.4-r0
- Debian DEBIAN-CVE-2026-3195 qemu Fixed in: 1:10.0.10+ds-0+deb13u1
- Ubuntu UBUNTU-CVE-2026-3195 qemu
References
- advisory nvd.nist.gov
- advisory access.redhat.com
- advisory github.com
- package gitlab.com
- report bugzilla.redhat.com
- web github.com
- web security.access.redhat.com
- web access.redhat.com