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.

Created attachment 1819165 [details]
Patch with suggested fixes

Description of problem:
As part of the RHEL 9 common criteria preparations, a review was done of coverity results to see if there are any problems found in the important results. Overall there were only 3 items that appear to be real bugs. All of them being resource leaks.

The coverity scan used is here:
https://cov01.lab.eng.brq.redhat.com/covscanhub/task/229105/log/glibc-2.34-2.el9/scan-results-imp.err

The real problems are these:

glibc-2.34/elf/ldconfig.c:506: leaked_storage:
iconv/gconv_parseconfdir.h:159: leaked_storage
iconv/iconv_charmap.c:238: leaked_storage

Additional info:
A patch with suggested fixes will be attached to expedite resolution.

I've kept bug 1938727 open to ensure that the scans remain clean for glibc through to release.  These specific issues should be fixed by the next rebase, i.e. bug 1994653 since they're fixed upstream[1][2][3] in release/2.34/master.

[1] https://sourceware.org/git/?p=glibc.git;a=commit;h=9995d0588f4f9adc68419224d2b3698e2ca4f77e
[2] https://sourceware.org/git/?p=glibc.git;a=commit;h=3a48da47a91ccc6f5de260574809e7a44551b876
[3] https://sourceware.org/git/?p=glibc.git;a=commit;h=0b03996304f86d6dba8f0d4b7048b9bb7186f17d

*** This bug has been marked as a duplicate of bug 1938727 ***