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 1646373 - glibc: Crash in getaddrinfo_a when thread creation fails
Summary: glibc: Crash in getaddrinfo_a when thread creation fails
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: DJ Delorie
QA Contact: qe-baseos-tools-bugs
Depends On: 1646379 1646381
Blocks: 1660844
TreeView+ depends on / blocked
Reported: 2018-11-05 13:29 UTC by Florian Weimer
Modified: 2019-08-06 12:49 UTC (History)
7 users (show)

Fixed In Version: glibc-2.17-269.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1646379 1646381 (view as bug list)
Last Closed: 2019-08-06 12:49:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2118 0 None None None 2019-08-06 12:49:33 UTC
Sourceware 22927 0 None None None 2019-07-01 14:53:33 UTC

Description Florian Weimer 2018-11-05 13:29:25 UTC
From the upstream bug report:

At line 237 in gai_misc.c:

lastp = requests_tail;
if (requests_tail == NULL)
  requests = requests_tail = newp;
else ...

If requests_tail was NULL then lastp remains NULL. 
Unfortunately if gai_create_helper_thread fails, lastp is de-referenced at line 267 which will cause a SIGSEGV.

Comment 1 Florian Weimer 2018-11-05 13:30:00 UTC
This should be reproducible with a custom malloc which fails after the right number of allocations.

Comment 3 Florian Weimer 2018-11-05 13:54:12 UTC
Upstream commit:

commit bd3b0fbae33a9a4cc5e2daf049443d5cf03d4251
Author: Andreas Schwab <schwab>
Date:   Mon Nov 5 12:47:30 2018 +0100

    libanl: properly cleanup if first helper thread creation failed (bug 22927)

Comment 6 Sergey Kolosov 2019-06-27 09:45:08 UTC
Verified with modified __gai_create_helper_thread() function which always returns -1 and a test that calls getaddrinfo_a(). In glibc-2.17-269.el7 getaddrinfo_a() doesn't crash but returns EAGAIN.

Comment 9 errata-xmlrpc 2019-08-06 12:49:05 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.


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