Xilinx Run Time (XRT): Improper Resource Locking
CVE-2025-0003 is a high-severity improper resource locking vulnerability in Xilinx Run Time (XRT) from AMD, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Xilinx Run Time (XRT) you run against the affected versions below, and install the vendor's latest release.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AMD | Xilinx Run Time (XRT) | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L. Scored by CNA (amd.com).
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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Resource Locking
The product must have exclusive access to a resource, but it does not lock or does not correctly lock that resource.
How developers prevent this class of flaw
- Use synchronization when locking a resource.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Xilinx Run Time (XRT)
- 8.0 High severity
- 7.3 High severity
- 7.3 High severity
Recent Improper Resource Locking vulnerabilities
- 10.0 Critical severity
- 7.7 High severity
Spotted an error? Tell us.