+++ This bug was initially created as a clone of Bug #905877 +++ This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please use the bodhi submission link noted in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the Bodhi notes field when available. Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please ensure that it is only closed when all affected versions are fixed. [bug automatically created by: add-tracking-bugs] --- Additional comment from Jan Lieskovsky on 2013-01-30 06:18:14 EST --- Please use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. Please also ensure that the "Close bugs when update is stable" option remains checked. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=905874,905877 --- Additional comment from Eric Blake on 2013-03-15 13:28:22 EDT --- We've got people panicking that this CVE is still unpatched in Fedora 18, and causing segfaults to appear during 'configure' runs: https://www.redhat.com/archives/libvir-list/2013-March/msg00951.html Any word on when fixed glibc will be released into Fedora? --- Additional comment from Carlos O'Donell on 2013-03-15 14:26:49 EDT --- I'll fix this before Monday and get rawhide and F18 updated. We already have a well reviewed patch for update. --- Additional comment from Carlos O'Donell on 2013-03-17 20:37:45 EDT --- Fixed in rawhide. Working on F18 and F19. --- Additional comment from Carlos O'Donell on 2013-03-17 23:58:14 EDT --- Fixed in F19. Koji build here: http://koji.fedoraproject.org/koji/taskinfo?taskID=5135287 The F18 patch needed some more pre-requisites to be backported. Thus local testing for F18 is not yet complete. --- Additional comment from Carlos O'Donell on 2013-03-18 13:23:42 EDT --- This tracks the f18 fix. --- Additional comment from Carlos O'Donell on 2013-03-18 13:44:34 EDT --- Fixed in F18. Koji build here: http://koji.fedoraproject.org/koji/taskinfo?taskID=5138634
This tracks the F17 fix.
Koji build for F17: http://koji.fedoraproject.org/koji/taskinfo?taskID=5143544
glibc-2.15-59.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/glibc-2.15-59.fc17
The previous bodhi update received a server error so I deleted the update, retagged the koji build and resumitted the update without error this time.
Package glibc-2.15-59.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.15-59.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4174/glibc-2.15-59.fc17 then log in and leave karma (feedback).
glibc-2.15-59.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.