CVE-2025-0003VulnerabilityPublished 24 Nov 2025

CVE-2025-0003: AMD Xilinx Run Time (XRT) · Improper Resource Locking

Affects AMD Xilinx Run Time (XRT)Source CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor AMD and Xilinx official channels for patches addressing CVE-2025-0003 and apply them promptly once released. 2. Restrict local access to systems running XRT to trusted users only, employing strict access controls and least privilege principles. 3. Implement endpoint detection and response (EDR) solutions to monitor for unusual activity related to XRT processes or memory corruption indicators. 4. Conduct regular audits of user accounts and running processes on systems with XRT installed to detect unauthorized usage. 5. Use application whitelisting to prevent execution of unauthorized code that could exploit the vulnerability. 6. Educate users about the risks of interacting with untrusted applications or files that could trigger the vulnerability. 7. In environments where patching is delayed, consider isolating FPGA-accelerated systems from general user access or network segments to reduce attack surface. 8. Employ runtime protections such as memory corruption mitigations (e.g., ASLR, DEP) if supported by the platform. 9. Review and harden system configurations related to XRT and FPGA management interfaces to minimize exposure. 10. Prepare incident response plans specific to FPGA-related vulnerabilities and ensure readiness to respond to potential exploitation attempts.

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

Impact

For European organizations, the impact of CVE-2025-0003 can be substantial, especially in sectors relying on FPGA technology for critical operations such as telecommunications, automotive, industrial automation, and research institutions. Loss of confidentiality could expose sensitive intellectual property or personal data processed by FPGA-accelerated applications. Availability impacts could disrupt services dependent on FPGA computations, leading to operational downtime or degraded performance. Since the vulnerability requires local access and user interaction, insider threats or compromised endpoints pose the greatest risk. Organizations with extensive use of Xilinx FPGA platforms in data centers or edge computing environments may face increased exposure. The confidentiality impact is critical, potentially allowing unauthorized data disclosure, while availability impact could lead to denial of service conditions. Integrity impact is lower but still present due to possible memory corruption. The vulnerability could also be leveraged as a stepping stone for privilege escalation or lateral movement within networks if combined with other vulnerabilities.

CWE-413Improper Resource Locking (opens in a new tab)
Base weakness
The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.
Architecture and Design
Use a non-conflicting privilege scheme.
Architecture and Design · Implementation
Use synchronization when locking a resource.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

amd.com/en/resources/product-security/bulletin/AMD-SB-8014.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Nov 2025, 20:55 UTC

WeaknessesCWE-413

Technical details

References

Community reviews

Related threats