CVE-2022-26942
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 Motorola MTM5000 series firmwares lack pointer validation on arguments passed to trusted execution environment (TEE) modules. Two modules are used, one responsible for KVL key management and the other for TETRA cryptographic functionality. In both modules, an adversary with non-secure supervisor level code execution can exploit the issue in order to gain secure supervisor code execution within the TEE. This constitutes a full break of the TEE module, exposing the device key as well as any TETRA cryptographic keys and the confidential TETRA cryptographic primitives.
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 Motorola MTM5000 series firmware lacks pointer validation on arguments passed to Trusted Execution Environment (TEE) modules, specifically in the KVL key management and TETRA cryptographic modules. An attacker with non-secure supervisor level code execution can exploit this to achieve secure supervisor code execution within the TEE, completely breaking the TEE security boundary and exposing device keys, TETRA cryptographic keys, and confidential cryptographic primitives.
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 versionsall 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 the device modelCheck the device hardware label, system information, or management interface for the exact model number. Look for 'MTM5500' or 'MTM5400' designations.Affected if The device is NOT a Motorola MTM5500 or MTM5400 unit - those are the only affected models.
-
Confirm firmware versionAccess the device's firmware version through its administrative interface, boot diagnostics, or by querying the system information endpoint. Record the installed firmware version string.Affected if Any firmware version is present on an MTM5500 or MTM5400 device, since all versions are affected according to the provided advisory.
-
Verify TEE module configurationExamine the device configuration or system logs for the presence and status of the KVL key management module and TETRA cryptographic module. These are the specific TEE modules referenced in the advisory.Affected if The KVL key management or TETRA cryptographic TEE modules are enabled or loaded on the device.
-
Assess non-secure supervisor access riskReview access controls, audit logs, and authentication mechanisms to determine whether an attacker could potentially achieve non-secure supervisor level code execution. Check for unauthorized access indicators or privilege escalation paths.Affected if The device permits or has documented vulnerabilities that could allow non-secure supervisor level code execution, which is required to exploit this TEE flaw.
If the device is a Motorola MTM5500 or MTM5400 with any firmware version and has the KVL or TETRA TEE modules active, and an attacker could achieve non-secure supervisor code execution, the environment is affected by this CVE.
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 dataApply vendor-provided firmware patches when available. Until then, restrict physical access and prevent unauthorized code execution at the non-secure supervisor level to reduce attack surface. Consider re-keying devices after applying the update.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26942 — 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-26942 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