dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-26353

HIGH · 7.5 CVSS v3.1 Published 2022-03-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

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 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.

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

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
QemuApplication
Affected:= 6.2.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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
Patch available Apply the vendor patch
Vendor patch gitlab.com →
Recommended fix Moderate confidence

QEMU 6.2.1 or later stable release (or Debian-packaged version with security fix applied)

  1. 1. Identify the QEMU version currently installed: `qemu-system-x86_64 --version` or `dpkg -l | grep qemu`
  2. 2. Obtain the fixed QEMU version. According to the QEMU release cycle, version 6.2.0 contained this bug. The fix was integrated into later point releases. Check for QEMU 6.2.1 or later, or the latest stable 6.2.x release from https://www.qemu.org/download/
  3. 3. For Debian 11 (bullseye) systems: Run `apt update` followed by `apt install qemu-system-x86` or `apt upgrade` to get the patched version from Debian's security updates
  4. 4. Verify the fix was applied by checking the running QEMU version after update: `qemu-system-x86_64 --version`
  5. 5. If using QEMU in a virtual machine manager (libvirt/KVM), restart any running VMs to ensure they use the updated QEMU binary
Caveat Minor version upgrade within 6.2.x should have minimal breaking changes; however, always test VM configurations with updated QEMU in a non-production environment first

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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