# CVE-2025-54515: The Secure Flag passed to Versal™ Adaptive SoC’s Trusted Firmware for Cortex®-A processors (TF-A) for Arm’s Power State Coordination Interfa


- **Severity:** Low 1.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Nov 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-hh36-fjhw-7fj3

## What is CVE-2025-54515?

CVE-2025-54515 is a low-severity vulnerability in AMD Alveo™ V80 Compute Accelerator, published on 23 Nov 2025. 

### Official description

The Secure Flag passed to Versal™ Adaptive SoC’s Trusted Firmware for Cortex®-A processors (TF-A) for Arm’s Power State Coordination Interface (PSCI) commands were incorrectly set to secure instead of using the processor’s actual security state. This would allow the PSCI requests to appear they were from processors in the secure state instead of the non-secure state.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2025-54515?


## How do I fix CVE-2025-54515?

No fix has been published for CVE-2025-54515 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-54515 being exploited?

There is no known exploitation of CVE-2025-54515 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54515 and fix it if it is affected.

What it is: CVE-2025-54515 is a low-severity vulnerability in AMD Alveo™ V80 Compute Accelerator, published on 23 Nov 2025. 
Exploitation: There is no known exploitation of CVE-2025-54515 in the wild and no public exploit code.

Affected product: AMD Alveo™ V80 Compute Accelerator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54515/ (Markdown: https://insights.sbomify.com/CVE-2025-54515/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54515
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54515
- OSV: https://osv.dev/vulnerability/CVE-2025-54515

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54515/
Summaries are generated and may contain mistakes; the official description above is the record.