Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause: The DNS stub resolver in glibc did not check for a failure to allocate name server data.
Consequence: If the allocation failed, the process would crash due to a null pointer dereference.
Fix: The stub resolver now checks for failures when allocating name server data.
Result: The allocation error is reported to the caller, leading to a name resolution failure, but no process crash.
This was reported upstream as a reliability issue. Fix:
commit f178e59fa5eefbbd37fde040ae8334aa5c857ee1
Author: Andreas Schwab <schwab>
Date: Tue Mar 27 12:16:11 2018 +0200
Fix crash in resolver on memory allocation failure (bug 23005)
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://access.redhat.com/errata/RHSA-2018:3092
This was reported upstream as a reliability issue. Fix: commit f178e59fa5eefbbd37fde040ae8334aa5c857ee1 Author: Andreas Schwab <schwab> Date: Tue Mar 27 12:16:11 2018 +0200 Fix crash in resolver on memory allocation failure (bug 23005)