A minor issue that does not affect the versions of glibc in RHEL or Fedora was reported: The issue was introduced in glibc 2.22, with commit 2212c1420c92a33b0e0bd9a34938c9814a56c0f7 (which also caused other regressions, which is why we backed it out in Fedora). The leak is triggered if name resolution functions are called in such a way that internal resolver data structures are only initialized partially. The memory leak was independently reported as occurring during Apache httpd testing, so we found it prudent to treat it as a very minor security vulnerability. Reference: http://seclists.org/oss-sec/2016/q3/225 Upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1305132