CVE-2022-25333
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 · uneditedThe Texas Instruments OMAP L138 (secure variants) trusted execution environment (TEE) performs an RSA check implemented in mask ROM when loading a module through the SK_LOAD routine. However, only the module header authenticity is validated. An adversary can re-use any correctly signed header and append a forged payload, to be encrypted using the CEK (obtainable through CVE-2022-25332) in order to obtain arbitrary code execution in secure context. 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 confidenceThe TEE on TI OMAP L138 secure variants performs RSA signature validation only on module headers during the SK_LOAD routine, not on the full payload. An attacker with access to the CEK (from CVE-2022-25332) can reuse any valid signed header and append a forged payload, encrypting it with the CEK to achieve arbitrary code execution in secure context, completely breaking the TEE security architecture.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device hardware modelCheck the system-on-chip or processor model via /proc/cpuinfo, boot logs, or hardware markings. Look for 'OMAP L138' or 'DM3730' variants from Texas Instruments.Affected if The device uses a TI OMAP L138 processor in its secure variant.
-
Confirm secure boot configurationInspect boot logs or secure boot status registers via debug interfaces. Check if secure boot is enabled in bootloader configuration (e.g., U-Boot environment variables showing 'secure boot' or ' huk/cek' keys loaded).Affected if Secure boot is enabled and the device uses the SK_LOAD routine for module loading.
-
Verify custom module loading capabilityExamine if the firmware loads external or custom signed modules. Check for SK_LOAD-related configurations in the boot process, custom .mod or header files being loaded at runtime.Affected if The system loads signed modules via the SK_LOAD routine (not factory-programmed code only).
-
Check for CEK exposure riskReview whether the CEK (Content Encryption Key) has been extracted or is accessible. This typically requires JTAG, debug ports, or side-channel analysis - check physical security and debug port accessibility.Affected if The CEK from CVE-2022-25332 is compromised or accessible to an attacker.
The system is affected if it runs on a TI OMAP L138 secure variant with custom module loading enabled and the CEK is accessible to an attacker.
Generated from the published advisory. Verify against your own configuration.
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 dataThis is a fundamental flaw in the mask ROM secure boot implementation requiring a firmware/microcode update from Texas Instruments to implement full-module signature validation rather than header-only validation, plus rotation of the CEK to prevent exploitation with the compromised key.
- Consultation40.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25333 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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