RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1313308 - invalid fastbin entry (free), missing glibc patch
Summary: invalid fastbin entry (free), missing glibc patch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.0
Hardware: Unspecified
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1305406
Blocks: 1097825
TreeView+ depends on / blocked
 
Reported: 2016-03-01 11:23 UTC by Jaroslav Reznik
Modified: 2019-11-14 07:31 UTC (History)
21 users (show)

Fixed In Version: glibc-2.17-106.el7_2.6
Doc Type: Bug Fix
Doc Text:
Previously, certain code paths used by the C library's memory allocator "fastbins" feature, which were enabled by default, were not thread-safe. When the non-safe code paths executed, the code paths could cause corruption in the allocator, which cause the application terminate unexpectedly with a segmentation fault. The thread-unsafe code paths have been made thread-safe, and the described problem no longer occurs.
Clone Of: 1305406
Environment:
Last Closed: 2016-05-12 09:59:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2173041 0 None None None 2016-03-01 11:23:33 UTC
Red Hat Product Errata RHBA-2016:1030 0 normal SHIPPED_LIVE glibc bug fix update 2016-05-12 13:54:50 UTC
Sourceware 15073 0 None None None 2019-08-05 09:35:53 UTC

Description Jaroslav Reznik 2016-03-01 11:23:23 UTC 
This bug has been copied from bug #1305406 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 8 Michael Petlan 2016-04-22 16:39:59 UTC 
Presence of the patch checked in glibc-2.17-106.el7_2.106 build tree.
Comment 9 Michael Petlan 2016-04-22 17:42:59 UTC 
Since there is no reliable reproducer, we have to be content with SanityOnly here.
Comment 11 errata-xmlrpc 2016-05-12 09:59:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1030.html
Note You need to log in before you can comment on or make changes to this bug.