Bug 1774114 - ldconfig: handle .dynstr located in separate segment (bug 25087)
Summary: ldconfig: handle .dynstr located in separate segment (bug 25087)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.3
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1819440 1825061
TreeView+ depends on / blocked
 
Reported: 2019-11-19 15:59 UTC by Carlos O'Donell
Modified: 2023-07-18 14:30 UTC (History)
9 users (show)

Fixed In Version: glibc-2.28-107.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:32:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4444 0 None None None 2020-11-04 01:33:13 UTC
Sourceware 25087 0 P2 RESOLVED ldconfig mishandles unusual .dynstr placement 2020-10-13 07:05:14 UTC

Description Carlos O'Donell 2019-11-19 15:59:04 UTC 
Backport this commit to fix defects loading files modified by patchelf.

commit 58e8f5fd2ba47b6dc47fd4d0a35e4175c7c87aaa
Author: Andreas Schwab <schwab>
Date:   Wed Oct 9 17:46:47 2019 +0200

    ldconfig: handle .dynstr located in separate segment (bug 25087)
    
    To determine the load offset of the DT_STRTAB section search for the
    segment containing it, instead of using the load offset of the first
    segment.
Comment 5 Sergey Kolosov 2020-09-07 10:33:54 UTC 
Verified with https://sourceware.org/bugzilla/show_bug.cgi?id=23964#c0 instructions.
Comment 8 errata-xmlrpc 2020-11-04 01:32:42 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 (Moderate: glibc security, bug fix, and enhancement update), 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-2020:4444
Note You need to log in before you can comment on or make changes to this bug.