Tobias Frauenschläger 85dd923355 cryptocb: always run software cleanup in key Free functions ...

The WOLF_CRYPTO_CB_FREE path in wc_MlKemKey_Free, wc_dilithium_free,
and wc_ecc_free returned early when the crypto callback succeeded,
skipping local cleanup: ForceZero on private key material, PRF/hash
object frees (ML-KEM), SHAKE free and cached vector frees (ML-DSA),
and mp_forcezero on the private scalar and all hardware port frees
(ECC).

Any non-PKCS#11 callback returning 0 would silently leave key material
in memory. The PKCS#11 backend worked around this by returning
CRYPTOCB_UNAVAILABLE on success to force the fallthrough — a fragile
contract that is not part of the documented callback interface.

Fix by always continuing to software cleanup after invoking the
callback.

Remove the CRYPTOCB_UNAVAILABLE workaround from the three PKCS#11 free
dispatchers (ECC, ML-DSA, ML-KEM); they now return the real result of
C_DestroyObject.

2026-04-10 12:23:57 +02:00

..

benchmark

globally fix all "BLAKE2" references (implicit BLAKE2B) to explicit "BLAKE2B":

2026-04-07 13:18:53 -05:00

src

cryptocb: always run software cleanup in key Free functions

2026-04-10 12:23:57 +02:00

test

PKCS#11: add ML-KEM support

2026-04-10 12:23:37 +02:00