Fix possible buffer leak in ChipLinuxStorageIni::GetBinaryBlobValue (#2856)
Fix possible buffer leak in ChipLinuxStorageIni::GetBinaryBlobValue (#2856)

It's possible for us to allocate encodedData but then never reach the
Base64Decode call because of failing buffer length checks (e.g. if the
encodedData buffer is more than 65KB).  So we should make sure we free
encodedData as long as it's not null.
nestlabs/connectedhomeip,nestlabs/connectedhomeip,nestlabs/connectedhomeip,project-chip/connectedhomeip,nestlabs/connectedhomeip,project-chip/connectedhomeip,project-chip/connectedhomeip,nestlabs/connectedhomeip,project-chip/connectedhomeip,project-chip/connectedhomeip,project-chip/connectedhomeip,nestlabs/connectedhomeip,nestlabs/connectedhomeip