CVE-2025-0040: JTAG/AXI Privilege Escalation Vulnerability

CVE-2025-0040 Overview

CVE-2025-0040 describes an improper access control weakness between the Joint Test Action Group (JTAG) debug interface and the Advanced Extensible Interface (AXI) bus in affected AMD products. An attacker with physical access can read or overwrite the contents of cross-chip debug (XCD) registers through this path. Successful exploitation can compromise data confidentiality and integrity on the targeted hardware.

The issue is tracked under [CWE-284: Improper Access Control] and requires physical interaction with the device. AMD has documented the flaw in two security bulletins covering the affected silicon. No public exploit code or in-the-wild exploitation has been reported.

Critical Impact
Physical attackers can manipulate XCD registers via the JTAG-to-AXI path, undermining the confidentiality and integrity of data processed by the chip.

Affected Products

AMD products listed in AMD Security Bulletin AMD-SB-4017
AMD products listed in AMD Security Bulletin AMD-SB-6027
Systems exposing JTAG debug interfaces to untrusted physical access

Discovery Timeline

2026-05-15 - CVE-2025-0040 published to the National Vulnerability Database (NVD)
2026-05-15 - Last updated in NVD database

Technical Details for CVE-2025-0040

Vulnerability Analysis

The vulnerability resides at the boundary between two on-chip interfaces. JTAG provides standardized boundary-scan and debug functionality, while AXI is the on-chip interconnect that routes transactions between intellectual property blocks. Access from the JTAG controller to AXI-mapped registers is not properly restricted in the affected designs.

Cross-chip debug (XCD) registers control sensitive debug state shared between dies or chiplets. Because the JTAG path can reach these registers through AXI without sufficient authorization checks, an attacker with debug-pin access can read protected values or write attacker-controlled content. The result is a loss of confidentiality and integrity for data accessible through those registers.

Root Cause

The root cause is missing or insufficient access control between the JTAG interface and the AXI fabric. The hardware design does not enforce that JTAG-initiated transactions targeting XCD registers carry the privileges required for those registers. This maps to [CWE-284].

Attack Vector

Exploitation requires physical access to the device and the ability to interact with JTAG test points or debug headers. The attacker connects debug tooling, issues transactions that traverse the JTAG-to-AXI bridge, and reads or writes XCD register values. Attack complexity is high because it depends on physical access, exposed pins, and chip-specific knowledge. Public proof-of-concept code is not available, and the vulnerability is described in prose only within the AMD advisories.

Detection Methods for CVE-2025-0040

Indicators of Compromise

Physical evidence of tampering with the device chassis, BGA package, or debug headers
Unexpected JTAG cabling, probes, or test fixtures attached to production hardware
Anomalous boot or attestation measurements that do not match the known-good baseline
Discrepancies in platform integrity logs that suggest debug-mode entry on production silicon

Detection Strategies

Monitor platform attestation and measured boot outputs for deviations from baseline values
Inspect production hardware for enabled debug fuses or unblown one-time-programmable (OTP) bits intended to disable JTAG
Correlate physical access logs from data center or facility systems with security events on affected hosts
Track firmware and platform telemetry for unexpected reboots or debug-state transitions

Monitoring Recommendations

Forward hardware attestation events, BMC logs, and chassis intrusion alerts to a central analytics platform for correlation
Establish baselines for JTAG-disable fuse status across the fleet and alert on changes
Review supply-chain custody records for hardware deployed in untrusted environments

How to Mitigate CVE-2025-0040

Immediate Actions Required

Review AMD Security Bulletin AMD-SB-4017 and AMD Security Bulletin AMD-SB-6027 to identify affected SKUs in your environment
Apply the firmware or microcode updates referenced by AMD for each affected platform
Restrict physical access to systems containing affected processors using locked racks, tamper-evident seals, and access logging
Disable or fuse-off JTAG debug interfaces on production hardware where supported by the platform

Patch Information

AMD has published mitigations in security bulletins AMD-SB-4017 and AMD-SB-6027. Consult these advisories for the list of affected products, fixed firmware versions, and deployment guidance specific to each platform family.

Workarounds

Enforce physical security controls and tamper detection on all systems with affected silicon
Disable external debug headers in BIOS or platform firmware where the option is exposed
Decommission or isolate hardware that cannot receive the vendor-supplied firmware update
Treat hardware returning from untrusted custody as suspect and re-image or re-attest before reuse