Bug 448525

Summary: CVE-2007-1320 xen/qemu Cirrus LGD-54XX "bitblt" Heap Overflow [Fedora 9]
Product: [Fedora] Fedora Reporter: Glauber Costa <gcosta>
Component: kvmAssignee: Glauber Costa <gcosta>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 9CC: berrange, clalance, dwmw2, gcosta, hdegoede, katzj, sundaram
Target Milestone: ---Keywords: Reopened, Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=important,source=vendorsec,reported=20070307,public=20070420
Fixed In Version: 65-7.fc9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-02 16:18:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 237342    

Comment 1 Fedora Update System 2008-05-29 02:33:10 UTC 
kvm-65-7.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 2 Glauber Costa 2008-11-11 15:47:10 UTC 
It appears this beast is still alive.
CVE-2008-4539 is its new name.
Comment 3 Fedora Update System 2008-11-11 16:06:37 UTC 
kvm-65-11.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/kvm-65-11.fc9
Comment 4 Fedora Update System 2008-11-12 02:55:58 UTC 
kvm-65-11.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kvm'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-9571
Comment 5 Fedora Update System 2008-12-02 15:54:31 UTC 
kvm-65-13.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/kvm-65-13.fc9
Comment 6 Tomas Hoger 2008-12-02 16:18:40 UTC 
This should be dead and closed, security regression in the original fix should be handled as separate issue.