Xilinx/AMD port fixes for sanity checks on return values and psoc6 sanity check on input arg

[JacobBarthelmeh]

Batch of Fenrir reports

[wolfSSL-Fenrir-bot]

Fenrir Automated Review — PR #10467

Scan targets checked: wolfcrypt-port-bugs

No new issues found in the changed files. ✅

[Copilot]

Pull request overview

This pull request tightens error handling and argument validation in hardware-accelerated crypto ports, ensuring Xilinx/AMD SHA3 and AES-GCM wrapper APIs fail fast when underlying XSecure calls report errors, and preventing a NULL dereference in the PSoC6 SHA-512 init path.

Changes:

• Add return-value checks for XSecure SHA3 update/final/readhash calls and map failures to WC_HW_E.
• Add return-value checks for XSecure AES-GCM initialization/encrypt operations (with cleanup on failure) and initialization in decrypt.
• Add a NULL check for sha in PSoC6 wc_InitSha512_ex() before XMEMSET.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
wolfcrypt/src/port/xilinx/xil-sha3.c	Check XSecure SHA3 API return codes and return WC_HW_E on hardware failures.
wolfcrypt/src/port/xilinx/xil-aesgcm.c	Validate XSecure AES init/encrypt return values and ensure temporary buffer is freed on failure.
wolfcrypt/src/port/cypress/psoc6_crypto.c	Add sha == NULL guard in SHA-512 init to avoid NULL dereference.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.