fix: Validate TA-supplied pointers in secure-kernel syscalls

[bmolodan]

The copy helpers tee_svc_copy_to_user/tee_svc_copy_from_user and the live crypto syscalls (utee_hash_update/final, utee_cipher_init, cipher update, copy_in_attrs) dereferenced or memcpy'd TA-supplied pointer ranges with their tee_mmu_check_access_rights() guard commented out. A malicious or buggy TA could pass a NULL or wrapping range and drive an out-of-bounds copy in the secure world.

This port has no per-TA MMU/MPU context or region table, and every call site requests TEE_MEMORY_ACCESS_ANY_OWNER, so ownership cannot (and is not meant to) be enforced. Implement tee_mmu_check_access_rights() as the accessibility check that is meaningful here - reject NULL+len and address-space-wrapping ranges, mirroring cmse_check_address_range()'s end-of-range test on the non-secure boundary - and restore the guard at every live call site, including the copy_in_attrs path that stores unvalidated attribute buffers later memcpy'd by op_attr_secret_value_from_user.

Add a temporary CONFIG_APPS_ACCESS_RIGHTS_TEST negative test (mps2 AN505) that drives the guard with malformed ranges and asserts TEE_ERROR_ACCESS_DENIED.

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code cleanup/refactoring
• CI system update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules