What is CVE-2025-0008?
Insufficient verification of data authenticity may allow a local attacker to bypass Secure Debug Unlock (SDU), potentially resulting in unauthorized debug access.
The record classifies CVE-2025-0008 under weakness class CWE-347. 9 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 9 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 8.4 — High (derived from score)
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-11-10
Is CVE-2025-0008 being exploited?
It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.
Affected products and versions
- AMD: EPYC™ 7003 Series Processors, EPYC™ 7002 Series Processors, EPYC™ 7001 Series Processors, Ryzen™ 3000 Series Desktop Processors, Ryzen™ Threadripper™ PRO 3000 WX-Series Processors, Ryzen™ Threadripper™ PRO 5000 WX-Series Processors, EPYC™ Embedded 7003 Series Processors, EPYC™ Embedded 7002 Series Processors, EPYC™ Embedded 3000 Series Processors
How to fix CVE-2025-0008
No vendor patch reference has been recorded for CVE-2025-0008 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2025-0008
No threat campaign in the Threadlinqs corpus currently references CVE-2025-0008, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.