---
id: "CVE-2025-0008"
page: "https://infrastack.ai/live/CVE-2025-0008"
kind: "vulnerability"
aliases: ["CVE-2025-0008"]
title: "AMD EPYC Secure Debug Unlock bypass lets a privileged local attacker gain debug access"
severity: "high"
cvss: 8.4
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "AMD EPYC 7001", "fixed": ["NaplesPI-SP3_1.0.0.T"], "affected": "before NaplesPI-SP3_1.0.0.T", "ecosystem": "vendor"}, {"name": "AMD EPYC 7002", "fixed": ["RomePI-SP3_1.0.0.Q"], "affected": "before RomePI-SP3_1.0.0.Q", "ecosystem": "vendor"}, {"name": "AMD EPYC 7003", "fixed": ["MilanPI 1.0.0.G"], "affected": "before MilanPI 1.0.0.G", "ecosystem": "vendor"}, {"name": "AMD EPYC Embedded 3000", "fixed": ["SnowyOwl_SP4_SP4r2.1.1.0.I"], "affected": "before SnowyOwl_SP4_SP4r2.1.1.0.I", "ecosystem": "vendor"}, {"name": "AMD EPYC Embedded 7002", "fixed": ["EmbeddedRomePI-SP3 1.0.0.G"], "affected": "before EmbeddedRomePI-SP3 1.0.0.G", "ecosystem": "vendor"}, {"name": "AMD EPYC Embedded 7003", "fixed": ["EmbMilanPI-SP3 1.0.0.B"], "affected": "before EmbMilanPI-SP3 1.0.0.B", "ecosystem": "vendor"}]
ecosystems: []
tags: ["amd", "bios", "epyc", "firmware", "hardware", "infrastructure", "secure-debug"]
not_affected_if: ["managed-hosting"]
published_at: "2026-11-10T23:17:18+00:00"
first_seen_at: "2026-11-10T23:27:34+00:00"
updated_at: "2026-11-10T23:31:05+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0008", "first_seen_at": "2026-11-10T23:27:34+00:00"}, {"source": "analyst", "url": "https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3049.html", "first_seen_at": "2026-11-10T23:31:05+00:00", "cites": ["https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3049.html"]}]
exploit_sources: []
---

# AMD EPYC Secure Debug Unlock bypass lets a privileged local attacker gain debug access

Link for people: https://infrastack.ai/live/CVE-2025-0008 (this .md is for agents)

AMD-SB-3049: the SDU authorization key provisioned in the BIOS is insufficiently validated and may be modified. An attacker with Ring 0 privileges can bypass debug access protections. CVSS 4.0 8.4. AMD lists EPYC 7001/7002/7003 and EPYC Embedded 3000/7002/7003. No exploitation or PoC is mentioned; AMD says it found this internally.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:AMD EPYC 7001 affected before NaplesPI-SP3_1.0.0.T fixed NaplesPI-SP3_1.0.0.T
- vendor:AMD EPYC 7002 affected before RomePI-SP3_1.0.0.Q fixed RomePI-SP3_1.0.0.Q
- vendor:AMD EPYC 7003 affected before MilanPI 1.0.0.G fixed MilanPI 1.0.0.G
- vendor:AMD EPYC Embedded 3000 affected before SnowyOwl_SP4_SP4r2.1.1.0.I fixed SnowyOwl_SP4_SP4r2.1.1.0.I
- vendor:AMD EPYC Embedded 7002 affected before EmbeddedRomePI-SP3 1.0.0.G fixed EmbeddedRomePI-SP3 1.0.0.G
- vendor:AMD EPYC Embedded 7003 affected before EmbMilanPI-SP3 1.0.0.B fixed EmbMilanPI-SP3 1.0.0.B

## How to check

Check whether your servers use AMD EPYC 7001/7002/7003 or EPYC Embedded 3000/7002/7003 processors. Then compare the BIOS PI version (from the server vendor's BIOS release notes, or dmidecode -t bios) with the mitigated PI versions in AMD-SB-3049.

## Fix

Install a BIOS from your server/board vendor that includes AMD's mitigated PI: EPYC 7001 NaplesPI-SP3_1.0.0.T; 7002 RomePI-SP3_1.0.0.Q; 7003 MilanPI 1.0.0.G; Embedded 3000 SnowyOwl_SP4_SP4r2.1.1.0.I; Embedded 7002 EmbeddedRomePI-SP3 1.0.0.G; Embedded 7003 EmbMilanPI-SP3 1.0.0.B.

## Timeline

- 2026-11-10T23:27:34+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-0008
- 2026-11-10T23:31:05+00:00 analyst https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3049.html — Read AMD-SB-3049 (primary). Affected list and PI fixes from it. A fankh.github.io page calls this CVE a PAN-OS overflow; it contradicts AMD and was ignored. No social search (low-profile firmware issue, no exploitation reported). how_to_check not marked verified (dmidecode hint is mine).

## Documents

- [advisory] AMD-SB-3049 Secure Debug Unlock (SDU) Vulnerability https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3049.html

## From the sources

Insufficient verification of data authenticity may allow a local attacker to bypass Secure Debug Unlock (SDU), potentially resulting in unauthorized debug access.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_