nvme: use kfree_sensitive() for DH-HMAC-CHAP secrets
Status from this message: Thanks, applied to nvme-7.4.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nvme-sysfs: use kfree_sensitive() for DH-HMAC-CHAP secretsdrivers/ | +6 | 2 replies | |
| 2/2 | nvme-fabrics: use kfree_sensitive() for the old DH-HMAC-CHAP secretdrivers/ | +2 | 2 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Hannes Reinecke | Christoph Hellwig |
|---|---|---|
| 1/2 | R-b | R-b |
| 2/2 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] nvme: use kfree_sensitive() for DH-HMAC-CHAP secrets
The host side stores the raw DH-HMAC-CHAP secret ("DHHC-1:...") but frees it with plain kfree() in a few places, leaving the secret in freed slab until the memory is reused. Switch those kfrees to kfree_sensitive() so the contents are wiped on free.
This is a hardening-only series; it fixes no functional bug and changes no behaviour.
Martin George (2):
nvme-sysfs: use kfree_sensitive() for DH-HMAC-CHAP secrets
nvme-fabrics: use kfree_sensitive() for the old DH-HMAC-CHAP secret
drivers/nvme/host/fabrics.c | 4 ++-- drivers/nvme/host/sysfs.c | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-)
Signature · 1 line
2.53.0