How severe is CVE-2025-0003?

CVE-2025-0003 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity low, and availability low.

Is CVE-2025-0003 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-0003?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-0003 have an EU (EUVD) identifier?

Yes. CVE-2025-0003 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199002.

When was CVE-2025-0003 published?

CVE-2025-0003 was published on 2025-11-24 and last updated on 2026-06-17.

CVE-2025-0003

CVE-2025-0003 is a high-severity vulnerability with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-413.

Key facts

Severity: High (CVSS 3.x base score 7.3)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-199002
Weakness: CWE-413
Published: 2025-11-24
Last modified: 2026-06-17

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

Frequently asked questions

What is CVE-2025-0003?: 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
How severe is CVE-2025-0003?: CVE-2025-0003 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity low, and availability low.
Is CVE-2025-0003 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-0003?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-0003 have an EU (EUVD) identifier?: Yes. CVE-2025-0003 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199002.
When was CVE-2025-0003 published?: CVE-2025-0003 was published on 2025-11-24 and last updated on 2026-06-17.

References

https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-8014.html

Other CWE-413 vulnerabilities

CVE-2025-3450 — Critical (CVSS 10.0): An Improper Resource Locking vulnerability in the SDM component of B&R Automation Runtime versions before 6.3 and…
CVE-2023-28649 — High (CVSS 8.6): The Hub in the Snap One OvrC cloud platform is a device used to centralize and manage nested devices connected to it. A…
CVE-2019-8998 — High (CVSS 7.8): An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the…
CVE-2022-49737 — High (CVSS 7.7): In X.Org X server 20.11 through 21.1.16, when a client application uses easystroke for mouse gestures, the main thread…
CVE-2026-32748 — High (CVSS 7.5): Squid is a caching proxy for the Web. Prior to version 7.5, due to premature release of resource during expected…
CVE-2023-33951 — Medium (CVSS 6.7): A race condition vulnerability was found in the vmwgfx driver in the Linux kernel. The flaw exists within the handling…

Browse all CWE-413 vulnerabilities →