Fix issue with opdata memory initialization

Change-Id: I6c3e7663b014cc10edd8f8409874d334706f78eb Signed-off-by: Steve Linsell <stevenx.linsell@intel.com>
intel · Sep 4, 2017 · d9369b9 · d9369b9
1 parent d931d66
commit d9369b9
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/qat_dh.c b/qat_dh.c
@@ -230,6 +230,8 @@ int qat_dh_generate_key(DH *dh)
         return ok;
     }
 
+    memset(opData, 0, sizeof(CpaCyDhPhase1KeyGenOpData));
+
     opData->primeP.pData = NULL;
     opData->baseG.pData = NULL;
     opData->privateValueX.pData = NULL;
@@ -525,6 +527,8 @@ int qat_dh_compute_key(unsigned char *key, const BIGNUM *in_pub_key, DH *dh)
         return ret;
     }
 
+    memset(opData, 0, sizeof(CpaCyDhPhase2SecretKeyGenOpData));
+
     opData->primeP.pData = NULL;
     opData->remoteOctetStringPV.pData = NULL;
     opData->privateValueX.pData = NULL;

diff --git a/qat_ec.c b/qat_ec.c
@@ -314,6 +314,8 @@ int qat_ecdh_compute_key(unsigned char **outX, size_t *outlenX,
         return ret;
     }
 
+    memset(opData, 0, sizeof(CpaCyEcPointMultiplyOpData));
+
     opData->k.pData = NULL;
     opData->xg.pData = NULL;
     opData->yg.pData = NULL;