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.

+++ This bug was initially created as a clone of Bug #1211098 +++

Description of problem:

When audit modules provide path as the return value of the la_objsearch calls the name replaces whatever ld.so uses to find the DSO.  If the target DSO has an SONAME this is the SONAME. As a result the SONAME is not in the list by which the DSO is known. This usually is no problem. It becomes a problem when the SONAME is needed afterwards. One example is checking symbol and DSO versions.

Version-Release number of selected component (if applicable):
RHEL6 glibc

How reproducible:
As below

Steps to Reproduce:
ld.so crash when below both  conditions are met
1) audit modules provide path
2) dependent libary(ie what is recorded in NEEDED section) has dso versioning

Actual results:
ld.so crash

Expected results:
ld.so not to crash

Additional info:
Upstream bugzilla
https://sourceware.org/bugzilla/show_bug.cgi?id=18251

--- Additional comment from Kazu Yoshida on 2015-04-12 21:57:37 EDT ---

glibc-2.12-1.149.el6_6.5

--- Additional comment from RHEL Product and Program Management on 2015-04-12 22:00:41 EDT ---

Since this bug report was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Ulrich's patch posted upstream:

  https://sourceware.org/ml/libc-alpha/2015-11/msg00112.html

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

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/RHSA-2016-2573.html