Report information
The Basics
Id:
43262
Status:
resolved
Estimated:
45 minutes
Priority:
Low/Low
Queue:

People
BugTracker
Version Fixed:
4.4.0 4.3.5
Version Found:
4.3.4
Versions Affected:
(no value)
Versions Planned:
4.4.0 4.3.5
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
DHCP Server
Area:
bug

Dates
Created:Sat, 24 Sep 2016 02:26:04 -0400
Updated:Tue, 12 Dec 2017 07:38:34 -0500
Closed:Tue, 27 Sep 2016 15:12:31 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: Bluecat patch to fix problem in leasechain.c that was exposed by #41325 in 4.3.4
From Support ticket #10492, Fernando provides us with a fix to his own code (which I think was the performance related lease file stuff in #39078 which is switched on with --enable-binary-leases.) I also think it was the cleanup work we did in #41325 that exposed it. On Fri Sep 23 23:23:44 2016, fsoto@bluecatnetworks.com wrote: > Hello, > > This one is kind of embarrassing. > I'm reporting my own bug. :-)))) > > When calling lc_delete_all() with a leasechain that is already empty, > it will result in an attempt to call dfree on a null pointer and dhcpd > will log: > > dhcpd: dfree leasechain.c(673): free on null pointer. > > The lc_delete_all calls were wrapped with an ifdef condition before > 4.3.4, so we didn't detect that issue: > > #if defined (DEBUG_MEMORY_LEAKAGE) || \ > defined (DEBUG_MEMORY_LEAKAGE_ON_EXIT) > ... > #endif > > > Patch is attached ;-) > > Thanks, > Fernando I think this is just a logging problem - not a functional one? Patch submitted is attached. It looks pretty sane and simple to me.
Subject: leasechain_free_on_null.patch

Message body not shown because it is not plain text.