Stack overflow on SK_LOAD signature length field in Texas Instruments OMAP L138
Description
The Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) lacks a bounds check on the signature size field in the SK_LOAD module loading routine, present in mask ROM. A module with a sufficiently large signature field causes a stack overflow, affecting secure kernel data pages. This can be leveraged to obtain arbitrary code execution in secure supervisor context by overwriting a SHA256 function pointer in the secure kernel data area when loading a forged, unsigned SK_LOAD module encrypted with the CEK (obtainable through CVE-2022-25332). This constitutes a full break of the TEE security architecture.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2- Texas Instruments/OMAPv5Range: L138
Patches
Vulnerability mechanics
Root cause
"Missing bounds check on the signature size field in the SK_LOAD module loading routine allows a stack overflow."
Attack vector
An attacker must first obtain the CEK (via CVE-2022-25332) to encrypt a forged, unsigned SK_LOAD module. The attacker then supplies a module with an oversized signature field. Because the SK_LOAD routine lacks a bounds check on the signature size, the oversized signature overflows a stack buffer and overwrites a SHA256 function pointer in the secure kernel data area. This yields arbitrary code execution in secure supervisor context, fully breaking the TEE security architecture [ref_id=1].
Affected code
The vulnerability resides in the SK_LOAD module loading routine within the mask ROM of the Texas Instruments OMAP L138 (secure variants) trusted execution environment. The routine lacks a bounds check on the signature size field, causing a stack overflow when a module with a sufficiently large signature field is loaded. This overflow affects secure kernel data pages, including a SHA256 function pointer in the secure kernel data area [ref_id=1].
What the fix does
No patch is shown in the supplied bundle. The advisory does not specify a vendor fix for this CVE; the TETRA:BURST disclosure page lists recommended mitigations for other CVEs but does not include a remediation entry for CVE-2022-25334 [ref_id=1]. Without a published fix, asset owners are advised to consult their national or sectoral CERT for guidance.
Preconditions
- inputAttacker must possess the CEK (obtainable via CVE-2022-25332) to encrypt a forged SK_LOAD module.
- inputAttacker must be able to supply a forged SK_LOAD module with a signature size field exceeding the stack buffer capacity.
Generated on May 25, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
1- tetraburst.commitrerelated
News mentions
0No linked articles in our index yet.