CVE Intelligence
Medium

CVE-2025-54511 — Improper handling of insufficient privileges in the AMD Secure Processor (ASP) could allow an...

Improper handling of insufficient privileges in the AMD Secure Processor (ASP) could allow an attacker to provide an input value to a function without sufficient privileges and successfully write data, potentially resulting in loss of integrity of availability.

Published May 15, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: AMD

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 10% of scored CVEs · Oct 14, 2026
Affects
AMD
AMD Instinct™ MI210 and 4 more
CVSS base
5.3
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (AMD AMD Instinct™ MI210, AMD AMD Instinct™ MI250, AMD AMD Radeon™ PRO V520…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
AMD AMD Instinct™ MI210 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Instinct™ MI250 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ PRO V520 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ PRO V620 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD MI-25 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
Low
Availability (vulnerable system)
Low
Confidentiality (subsequent)
None
Integrity (subsequent)
None
Availability (subsequent)
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — psirt@amd.com via NIST National Vulnerability Database
5.3 CVSS 4.0 Medium — — AMD via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: psirt@amd.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-274

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · amd/mi-25, amd/amd instinct™ mi250, amd/amd instinct™ mi210, amd/amd radeon™ pro v520, amd/amd radeon™ pro v620
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 15, 2026 · AMD

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

AMD
every CVE for this vendor
CWE-274
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-43598 Untrusted Pointer Dereference in AMD AMD Instinct™ MI210 8d
  • CVE-2021-46747 Insufficient granularity of access control in ASP (AMD Secure Processor) may allow an… Jun 1, 2026
  • CVE-2026-0481 Unrestricted IP address binding in the AMD Device Metrics Exporter (ROCm ecosystem)… May 15, 2026
  • CVE-2025-52532 A race condition in the MxGPU-Virtualization driver’s ioctl path caused by concurrent... May 15, 2026
  • CVE-2025-66660 Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a… May 15, 2026
  • CVE-2025-54517 Out of bounds write in AMD AMDGV_CMD_GET_DIAG_DATA ioctl handler could allow a local user to... May 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-54511 is "Improper handling of insufficient privileges in the AMD Secure Processor (ASP) could allow an...", rated Medium. It affects AMD Instinct™ MI210 (AMD); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.