VirtualizationApplication · Redhat
CVE-2013-4535
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 · uneditedThe virtqueue_map_sg function in hw/virtio/virtio.c in QEMU before 1.7.2 allows remote attackers to execute arbitrary files via a crafted savevm image, related to virtio-block or virtio-serial read.
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 · high confidenceA buffer overflow vulnerability exists in the virtqueue_map_sg function in QEMU's virtio implementation (hw/virtio/virtio.c). Attackers can exploit this by presenting a crafted savevm image that triggers improper handling during virtio-block or virtio-serial device reads, allowing arbitrary file execution within the QEMU virtual machine context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
VirtualizationApplication
= 3.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux Server TusOperating system
= 6.5
Enterprise Linux WorkstationOperating system
= 6.0< 1.7.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed QEMU versionRun 'qemu-system-x86_64 --version' or 'rpm -q qemu-kvm' (Red Hat) or 'qemu --version' to determine the installed version numberAffected if The installed version is less than 1.7.2 or the version cannot be determined but falls within Red Hat Enterprise Linux 6.x/6.5 or Red Hat Virtualization 3.0 ranges
-
Confirm virtio-block or virtio-serial device usageInspect QEMU command line arguments or VM configuration files for '-device virtio-blk-pci' or '-device virtio-serial-pci' parameters indicating virtio devices are attachedAffected if The environment uses virtio-block or virtio-serial devices with the vulnerable QEMU version
-
Check for savevm image filesSearch for files with '.savevm' or similar savevm state file extensions in VM storage directories, or inspect VM configurations for 'loadvm' directives pointing to savevm imagesAffected if Savevm images exist in the environment and could be loaded by the vulnerable QEMU instance
-
Verify virtio driver is loaded in VMsInside the guest VM, check if virtio drivers are active: on Linux run 'lsmod | grep virtio' or check for virtio block devices at /dev/vd*Affected if The guest VM is using virtio block or serial drivers, which are required for the vulnerable code path to be exercised
The environment is affected if QEMU version is below 1.7.2 AND the VM uses virtio-block or virtio-serial devices AND savevm images from untrusted sources could be loaded.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.7.2
Update QEMU to version 1.7.2 or later to obtain the patched code. Until patching is possible, restrict access to savevm images from untrusted sources and isolate affected QEMU instances on restricted network segments.
Fix this in Virtualization
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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