We've been updating our OP-TEE version without updating our Rust definitions of its API types. Since the GlobalPlatform TEE Client API uses client-allocated API objects, our code needs to be aware of and match the implementation-specific fields used by the version of libteec we link to.
This pulls in two changes that we missed, one of which increases the space we need to allocate for TEEC_Context and so results in memory unsafety with our current definitions:
We've been updating our OP-TEE version without updating our Rust definitions of its API types. Since the GlobalPlatform TEE Client API uses client-allocated API objects, our code needs to be aware of and match the implementation-specific fields used by the version of libteec we link to.
This pulls in two changes that we missed, one of which increases the space we need to allocate for TEEC_Context and so results in memory unsafety with our current definitions: