From: unassigned <unassigned.56@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
unassigned <unassigned.56@gmail.com>
Subject: [PATCH 1/2] crypto: Update cleanup path to use kfree_sensitive()
Date: Sun, 19 Jul 2026 11:07:50 +0100 [thread overview]
Message-ID: <20260719100750.13867-1-unassigned.56@gmail.com> (raw)
---
drivers/crypto/xilinx/zynqmp-aes-gcm.c | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/crypto/xilinx/zynqmp-aes-gcm.c b/drivers/crypto/xilinx/zynqmp-aes-gcm.c
index d54c268dfe34..551726aac806 100644
--- a/drivers/crypto/xilinx/zynqmp-aes-gcm.c
+++ b/drivers/crypto/xilinx/zynqmp-aes-gcm.c
@@ -230,10 +230,8 @@ static int zynqmp_aes_aead_cipher(struct aead_request *req)
}
freemem:
- memzero_explicit(kbuf, dma_size);
- kfree(kbuf);
- memzero_explicit(dmabuf, sizeof(struct zynqmp_aead_hw_req) + GCM_AES_IV_SIZE);
- kfree(dmabuf);
+ kfree_sensitive(kbuf);
+ kfree_sensitive(dmabuf);
return ret;
}
@@ -364,11 +362,9 @@ static int versal_aes_aead_cipher(struct aead_request *req)
if (unlikely(dma_addr_hw_req))
dma_unmap_single(dev, dma_addr_hw_req, dmabuf_size, DMA_BIDIRECTIONAL);
buf2_free:
- memzero_explicit(dmabuf, dmabuf_size);
- kfree(dmabuf);
+ kfree_sensitive(dmabuf);
buf1_free:
- memzero_explicit(kbuf, kbuf_size);
- kfree(kbuf);
+ kfree_sensitive(kbuf);
err:
return ret;
}
--
2.47.3
next reply other threads:[~2026-07-19 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 10:07 unassigned [this message]
2026-07-20 0:13 ` [PATCH 1/2] crypto: Update cleanup path to use kfree_sensitive() Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260719100750.13867-1-unassigned.56@gmail.com \
--to=unassigned.56@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox