PARTEMU: Enabling Dynamic Analysis of Real-World TrustZone Software Using Emulation

 April 5, 2021 at 10:04 am


  • USENIX Security 2020
  • Paper
  • Source code unavailable

Traditional TrustZone OSes and Applications is not easy to fuzz because they cannot be instrumented or modified easily in the original hardware environment. So to emulate them for fuzzing purpose.


  • Emulate TrustZone OSes(TZOS) and Trusted Applications (TAs)
  • Abstract and reimplement a subset of hardware/software interfaces
  • Fuzz these components
  • TZOSes: QSEE, Huawei, OPTEE, Kinibi, TEEGRIS(Samsung) & TAs

Design & Method

  • Re-host the TZOS frimware
  • Choose the components to reuse/emulate carefully
    • Bootloader
    • Secure Monitor
    • TEE driver and TEE userspace
    • MMIO registers (easy to emulate)


  • TriforceAFL + QEMU
  • Manually written Interfaces


Emulations works well. For upgraded TZOSes, only a few efforts are needed for compatibility.



  • Identifying the fuzzed target
  • Result stability (migrate to hardware, reproducibility)
  • Randomness
ClassVulnerability TypesCrashes
AvailabilityNull-pointer dereferences9
Insufficient shared memory crashes10
ConfidentialityRead from attacker-controlled pointer to shared memory8
Read from attacker-controlled0
OOB buffer length to shared memory
IntegrityWrite to secure memory using attacker-controlled pointer11
Write to secure memory using2
attacker-controlled OOB buffer length

Just like the previous paper, the main causes of the crashes can be attributed to:

  • Assumptions of Normal-World Call Sequence
  • Unvalidated Pointers from Normal World
  • Unvalidated Types


  • Normal-World Checks
  • Assumptions of Normal-World Call Sequence



  • Solid work
  • Efforts taken to run TZOS and TA in emulation environment
  • Acceptable performance


  • Low coverage
  • Crashes -X-> vulnerabilities