# CVE-2025-0003: Use after free in Xilinx Run Time (XRT)

> A local attacker can exploit inadequate lock protection in Xilinx Run Time to trigger a use-after-free, compromising confidentiality and availability.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-3j2q-3qf9-5m6x

## What is CVE-2025-0003?

CVE-2025-0003 is a high-severity use after free vulnerability in AMD Xilinx Run Time (XRT), published on 24 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Inadequate lock protection within Xilinx Run time may allow a local attacker to trigger a Use-After-Free condition potentially resulting in loss of confidentiality or availability

Weakness: CWE-413 (Improper Resource Locking)

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


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

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

## Is CVE-2025-0003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0003 is a high-severity use after free vulnerability in AMD Xilinx Run Time (XRT), published on 24 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0003 in the wild and no public exploit code.

Affected product: AMD Xilinx Run Time (XRT). 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-0003/ (Markdown: https://insights.sbomify.com/CVE-2025-0003/index.md)
```

## Sources

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

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