Bug 1810146
Summary: | glibc: getaddrinfo: Fix resource leak after strdup failure in gethosts [BZ #25425] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Carlos O'Donell <codonell> |
Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs |
Severity: | unspecified | Docs Contact: | Zuzana Zoubkova <zzoubkov> |
Priority: | unspecified | ||
Version: | 8.3 | CC: | ashankar, codonell, dj, fweimer, lmanasko, mnewsome, pfrankli, sipoyare, skolosov |
Target Milestone: | rc | Keywords: | Patch, Triaged |
Target Release: | 8.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.28-112.el8 | Doc Type: | Bug Fix |
Doc Text: |
.`getaddrinfo` now correctly handles a memory allocation failure
Previously, after a memory allocation failure, the `getaddrinfo` function of the GNU C Library `glibc` did not release the internal resolver context. As a consequence, `getaddrinfo` was not able to reload the `/etc/resolv.conf` file for the rest of the lifetime of the calling thread, resulting in a possible memory leak.
This update modifies the error handling path with an additional release operation for the resolver context. As a result, `getaddrinfo` reloads `/etc/resolv.conf` with new configuration values even after an intermittent memory allocation failure.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 01:33:21 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: | 1819986 | ||
Bug Blocks: |
Description
Carlos O'Donell
2020-03-04 15:43:14 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 |