Fragmentation or memory leak in Secure World?

matt1024 — Tue, 07 Oct 2025 17:08:09 GMT

Hi,

I faced an Out-of-Memory (OOM) issue when I ran a test program to read the secure blob stored via a trusted application (TA).

I carefully observed the code, but I couldn't find any memory vulnerability.

The test program reads the symmetric keys and decrypts some of them with the given key through the TA.

It happened after at least 15 mins of execution, there was no error log from the TA and tee-os (only debugging message appeared).

I initially suspected that it came from memory leak, but it became less likely because of lack of error messages from TA and tee-os.

In other words, if there is memory leak at explicit allocation (e.g., via TEE_Malloc) from customized TA, it should be captured, but I've never seen such error messages in the TA.

Another pointer is that I used bstats() to see total free memory and maximum free memory before/after open_session, close_session, and command, all the memory was quite stable during the execution, but after giving

I have two questions regarding this.
- Is there an API to debug memory (in use vs free) in each TA.
- How fragmentation has been handled in qoriq-optee-os. Are there known issues regarding fragmentation issues if there are many calls to TA?

Re: Fragmentation or memory leak in Secure World?

zhxyu — Wed, 26 Nov 2025 01:01:04 GMT

Have you do long time test with plain text big buffer?Maybe no secure big buffer memory leak, also.

QorIQのトピックFragmentation or memory leak in Secure World?

Fragmentation or memory leak in Secure World?

Re: Fragmentation or memory leak in Secure World?