- Issued:
- 2010-05-26
- Updated:
- 2010-05-26
RHBA-2010:0441 - Bug Fix Advisory
Synopsis
glibc bug fix update
Type/Severity
Bug Fix Advisory
Topic
Updated glibc packages that fix a crash when using Asynchronous I/O (AIO)
are now available.
Description
The glibc packages contain the standard C libraries used by multiple
programs on the system. These packages contain the standard C and the
standard math libraries. Without these two libraries, the Linux system
cannot function properly.
This update applies the following bug fix:
- submitting an AIO write request initially requires creating a helper
thread to handle the request. If the creation of this thread fails, a
corruption of glibc internal data structures can result which can cause a
crash when the next AIO request is submitted. This update corrects this by
making sure the internal structures remain consistent. (BZ#589869)
All users are advised to upgrade to these updated packages, which resolve
this issue.
Solution
Before applying this update, make sure all previously-released errata
relevant to your system have been applied.
This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259
Affected Products
- Red Hat Enterprise Linux for x86_64 - Extended Update Support 5.3 x86_64
- Red Hat Enterprise Linux for x86_64 - Extended Update Support 5.3 ia64
- Red Hat Enterprise Linux for x86_64 - Extended Update Support 5.3 i386
- Red Hat Enterprise Linux Server - AUS 5.3 x86_64
- Red Hat Enterprise Linux Server - AUS 5.3 ia64
- Red Hat Enterprise Linux Server - AUS 5.3 i386
- Red Hat Enterprise Linux for IBM z Systems - Extended Update Support 5.3 s390x
- Red Hat Enterprise Linux for Power, big endian - Extended Update Support 5.3 ppc
Fixes
- BZ - 589869 - If pthread_create fails in aio_write, requests linked list is corrupted
CVEs
(none)
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.