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 1282488 - Address memory leaks in server-side GSS authenticator
Summary: Address memory leaks in server-side GSS authenticator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libtirpc
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Murphy Zhou
URL:
Whiteboard:
Depends On: 1282463
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-16 15:19 UTC by Steve Dickson
Modified: 2016-11-04 02:15 UTC (History)
5 users (show)

Fixed In Version: libtirpc-0.2.4-0.7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1282463
Environment:
Last Closed: 2016-11-04 02:15:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2280 0 normal SHIPPED_LIVE libtirpc bug fix update 2016-11-03 13:35:59 UTC

Description Steve Dickson 2015-11-16 15:19:29 UTC
+++ This bug was initially created as a clone of Bug #1282463 +++

[ Its not clear whether RHEL7 needs these fixes but we should ]
[ take a look ]

Description of problem:

There are additional memory leaks observed in the _gss_authenticate
code path originating in libgssapi_krb5, which remain unaddressed.
These might not be libtirpc problems.


Needed upstream patches:


commit c301db9dfd3f58ee1a286c5d421eb82c0daa5187
Author: Chuck Lever <chuck.lever>
Date:   Mon Nov 16 08:11:21 2015 -0500

    Fix svcauth_gss_accept_sec_context() memory leaks

commit d50a71515feda22c251ee3be4fc56de685866105
Author: Chuck Lever <chuck.lever>
Date:   Mon Nov 16 08:10:04 2015 -0500

    Fix XDR result leak in _svcauth_gss()

commit 169318cc0c97c9b92cb1c875e54a82cc8c41717c
Author: Chuck Lever <chuck.lever>
Date:   Mon Nov 16 08:05:45 2015 -0500

    Fix checksum buffer leak

commit 49896c3068a0a2e87028a7391ac9bf4725e08375
Author: Chuck Lever <chuck.lever>
Date:   Mon Nov 16 08:03:46 2015 -0500

    Fix memory leak in svcauth_gss_import_name()

commit 8cf197b50243dee64ffb6c2da1d92179bee4f705
Author: Chuck Lever <chuck.lever>
Date:   Mon Nov 16 08:01:29 2015 -0500

    rpc_gss_set_svc_name() overwrites _svcauth_gss_creds

Comment 8 errata-xmlrpc 2016-11-04 02:15:23 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-2280.html


Note You need to log in before you can comment on or make changes to this bug.