`getaddrinfo` leaks memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eglibc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Marc Deslauriers |
Bug Description
I believe 2.11.1-0ubuntu7.14 (Ubuntu 10.04) introduces a regression in `getaddrinfo`.
I'm using the test case from [Debian Bug #304022](https:/
(The host in the test case yields a NXDOMAIN, but this isn't significant; it seems 1 kB will be leaked per block in any case.)
==7== Memcheck, a memory error detector
==7== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==7== Using Valgrind-
==7== Command: ./a.out
==7==
==7==
==7== HEAP SUMMARY:
==7== in use at exit: 1,024 bytes in 1 blocks
==7== total heap usage: 58 allocs, 57 frees, 9,893 bytes allocated
==7==
==7== 1,024 bytes in 1 blocks are definitely lost in loss record 1 of 1
==7== at 0x4C274A8: malloc (vg_replace_
==7== by 0x4EE7EC6: gaih_inet (getaddrinfo.c:858)
==7== by 0x4EEA8F1: getaddrinfo (getaddrinfo.
==7== by 0x400606: main (in /tmp/a.out)
==7==
==7== LEAK SUMMARY:
==7== definitely lost: 1,024 bytes in 1 blocks
==7== indirectly lost: 0 bytes in 0 blocks
==7== possibly lost: 0 bytes in 0 blocks
==7== still reachable: 0 bytes in 0 blocks
==7== suppressed: 0 bytes in 0 blocks
==7==
==7== For counts of detected and suppressed errors, rerun with: -v
==7== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
CVE References
Changed in eglibc (Ubuntu): | |
status: | Confirmed → Incomplete |
status: | Incomplete → Confirmed |
Changed in eglibc (Ubuntu Lucid): | |
status: | New → Confirmed |
assignee: | nobody → Marc Deslauriers (mdeslaur) |
Changed in eglibc (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in eglibc (Ubuntu Lucid): | |
status: | Confirmed → In Progress |
Status changed to 'Confirmed' because the bug affects multiple users.