Fix potential memory leak when copying into existing SHA contexts and zero init tmpSha#9829

Draft

night1rider wants to merge 7 commits intowolfSSL:masterfrom

night1rider:tmpSha-fixes

Commits on Feb 25, 2026

Fix potential memory leak when copying into existing SHA contexts and zero-initialize temp GetHash contexts
night1rider
committed
Fix potential memory leak in SHA Copy and zero-initialize temp GetHash contexts; zero HMAC dst hash before copy to prevent shared pointers
night1rider
committed
memset 0 the temp contexts
night1rider
committed
Add Free(dst) + XMEMSET before XMEMCPY in all wc_ hash Copy functions (MD5, SHA, SHA2, SHA3, SHAKE) and add copy cleanup tests to prevent resource leaks when copying into previously-used contexts.
night1rider
committed
Fix SHA3/Shake copy cleanup tests to heap-allocate shaCopy to avoid exceeding stack frame limit.
night1rider
committed
Revert "Fix SHA3/Shake copy cleanup tests to heap-allocate shaCopy to avoid exceeding stack frame limit."
night1rider
committed
Use WC_DECLARE_VAR/WC_ALLOC_VAR for shaCopy in SHA3/Shake tests to avoid stack frame overflow on small-stack builds.
night1rider
committed