dbcve.org
Omap L138 FirmwareOperating system · Ti

CVE-2022-25334

HIGH · 8.8 CVSS v3.1 Published 2023-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Texas Instruments OMAP L138 secure variants contain a stack overflow vulnerability in the SK_LOAD module loading routine within mask ROM. The trusted execution environment lacks a bounds check on the signature size field, allowing a malicious module with an oversized signature to overflow the stack and overwrite secure kernel data, including a SHA256 function pointer. When chained with CVE-2022-25332 to obtain the CEK, this enables arbitrary code execution in secure supervisor context, completely breaking the TEE security architecture.

MitigationThis is a mask ROM vulnerability that cannot be directly patched; mitigations include implementing strict secure boot policies to prevent loading of unauthorized modules, and affected devices may require replacement or hardware revision. Contact TI for available secure boot workarounds and device-specific guidance.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Omap L138 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OMAP L138 hardware variant
    Check the specific part number on the device or in the BOM (Bill of Materials). Look for OMAP-L138 secure variants, which typically have 'secure' or 'S' in the product name (e.g., OMAPL138-xxxS). Use 'cat /proc/cpuinfo' or check device tree files if available on the system.
    Affected if The device uses a Texas Instruments OMAP L138 secure variant (secure SKU)
  2. Confirm secure boot configuration status
    Check if secure boot is enabled on the device. On TI OMAP L138, this is typically configured via efuse settings or boot pins. Consult TI technical documentation for the specific method to read secure boot status on this platform.
    Affected if Secure boot is not enabled or is in a permissive state, allowing unsigned or malicious module loading
  3. Review secure boot policy and module signing
    Examine the secure boot policy configuration to determine which module loading mechanisms are permitted. Check if module signature verification is enforced for SK_LOAD routines.
    Affected if Secure boot policy allows loading of modules without verified signatures or does not enforce signature validation on the SK_LOAD routine

The device is affected if it uses a Texas Instruments OMAP L138 secure variant, regardless of firmware version, particularly when secure boot is not properly enforcing module signature validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is a mask ROM vulnerability that cannot be directly patched; mitigations include implementing strict secure boot policies to prevent loading of unauthorized modules, and affected devices may require replacement or hardware revision. Contact TI for available secure boot workarounds and device-specific guidance.

Fix this in Omap L138 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25334 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data