Bug 698906 (CVE-2011-1750) - CVE-2011-1750 virtio-blk: heap buffer overflow caused by unaligned requests
Summary: CVE-2011-1750 virtio-blk: heap buffer overflow caused by unaligned requests
Alias: CVE-2011-1750
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 698909 698910 698911
TreeView+ depends on / blocked
Reported: 2011-04-22 08:50 UTC by Petr Matousek
Modified: 2021-02-24 15:34 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-07-29 12:40:58 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0534 0 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2011-05-19 11:20:36 UTC

Description Petr Matousek 2011-04-22 08:50:40 UTC
It was found that virtio-blk driver in qemu-kvm did not properly validate 
read and write requests from the guest. A privileged guest user could use
this flaw to cause heap corruption, causing the guest to crash (denial of
service) or, possibly, resulting in the privileged guest user escalating
their privileges on the host.

On RHEL ExecShield (glibc heap/memory checks) mitigates this issue.


Upstream commit:

Comment 4 Petr Matousek 2011-04-22 08:58:07 UTC
Created qemu tracking bugs for this issue

Affects: fedora-all [bug 698911]

Comment 7 errata-xmlrpc 2011-05-19 13:02:41 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0534 https://rhn.redhat.com/errata/RHSA-2011-0534.html

Comment 8 Petr Matousek 2012-03-30 17:34:17 UTC

This issue does not affect versions of kvm package as shipped with Red Hat
Enterprise Linux 5.

Comment 9 Fedora Update System 2012-06-07 23:06:38 UTC
qemu-0.14.0-9.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.