[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1648114692-11175-1-git-send-email-unSimple1993@163.com>
Date: Thu, 24 Mar 2022 17:38:12 +0800
From: QintaoShen <unSimple1993@....com>
To: herbert@...dor.apana.org.au
Cc: davem@...emloft.net, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, QintaoShen <unSimple1993@....com>
Subject: [PATCH v1] crypto: stm32: Check for NULL return of kmalloc_array()
As the potential failure of memory allocation, kmalloc_array() may return
NULL and lead to NULL pointer dereference because of the usage of 'rctx->hw_context'.
Therefore, it is better to check the return value of kmalloc_array().
Signed-off-by: QintaoShen <unSimple1993@....com>
---
drivers/crypto/stm32/stm32-hash.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/stm32/stm32-hash.c b/drivers/crypto/stm32/stm32-hash.c
index d33006d..f1a1a13 100644
--- a/drivers/crypto/stm32/stm32-hash.c
+++ b/drivers/crypto/stm32/stm32-hash.c
@@ -970,7 +970,8 @@ static int stm32_hash_export(struct ahash_request *req, void *out)
rctx->hw_context = kmalloc_array(3 + HASH_CSR_REGISTER_NUMBER,
sizeof(u32),
GFP_KERNEL);
-
+ if (!rctx->hw_context)
+ return -ENOMEM;
preg = rctx->hw_context;
*preg++ = stm32_hash_read(hdev, HASH_IMR);
--
2.7.4
Powered by blists - more mailing lists