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.

Bug 1211098

Summary:	ld.so crash when audit modules provide path
Product:	Red Hat Enterprise Linux 6	Reporter:	Kazu Yoshida <kyoshida>
Component:	glibc	Assignee:	Florian Weimer <fweimer>
Status:	CLOSED ERRATA	QA Contact:	Arjun Shankar <ashankar>
Severity:	high	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	high
Version:	6.6	CC:	apetrova, ashankar, bhubbard, codonell, fweimer, mmuehlfe, mnewsome, pfrankli
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	glibc-2.12-1.176.el6	Doc Type:	Release Note
Doc Text:	The dynamic linker (ld.so) does not fail anymore when an audit module provides a DSO path Previously, when an audit module provided an alternate DSO (dynamic shared object) path, the ld.so dynamic linker terminated unexpectedly with a segmentation fault. This update addresses the bug, and now the dynamic linker keeps track of the original DSO path for future reference and does not fail anymore.	Story Points:	---
Clone Of:
Clones:	1211100 (view as bug list)		Environment:
Last Closed:	2016-05-10 21:26:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1172231, 1271375

Description Kazu Yoshida 2015-04-13 01:48:28 UTC

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

Comment 1 Kazu Yoshida 2015-04-13 01:57:37 UTC

glibc-2.12-1.149.el6_6.5

Comment 9 Florian Weimer 2015-11-06 13:20:26 UTC

Ulrich's patch posted upstream:

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

Comment 17 errata-xmlrpc 2016-05-10 21:26:33 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-0834.html