Skip to content
Fencer Intel
medium 5.8

CVE-2011-2512 json

The virtio_queue_notify in qemu-kvm 0.14.0 and earlier does not properly validate the virtqueue number, which allows guest users to cause a…

published 2012-06-21 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2497

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

The virtio_queue_notify in qemu-kvm 0.14.0 and earlier does not properly validate the virtqueue number, which allows guest users to cause a denial of service (guest crash) and possibly execute arbitrary code via a negative number in the Queue Notify field of the Virtio Header, which bypasses a signed comparison.

Patch / fix

  • qemu-kvm RHEL 6 2:0.12.1.2-2.160.el6_1.2
  • qemu-img RHEL 6 2:0.12.1.2-2.160.el6_1.2
  • qemu-kvm-tools RHEL 6 2:0.12.1.2-2.160.el6_1.2

red hat advisories RHSA-2011:0919

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2512 updated cvss 6.5

qemu-kvm: OOB memory access caused by negative vq notifies

  • Red Hat Enterprise Linux Server (v. 6) qemu-img 0.12.1.2-2.160.el6_1.2, qemu-kvm 0.12.1.2-2.160.el6_1.2, qemu-kvm-tools 0.12.1.2-2.160.el6_1.2
    fixed: vendor fix RHSA-2011:0919
  • Red Hat Enterprise Linux 5 kvm
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.88% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:A/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.