CVE Intelligence
Low

CVE-2025-66660 — Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a…

Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a malformed DRV_SOC_CMD_ID_SRIOV_CHECK_TA_COMPAT to cause incorrect shared memory mapping, potentially resulting in unexpected behavior.

Published May 15, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · 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.1% (30-day exploitation probability)+0

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.1%
ahead of 1% of scored CVEs · Oct 14, 2026
Affects
AMD
AMD Instinct™ MI210 and 11 more
CVSS base
1.8
Low · 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 Instinct™ MI300A…).
  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 Instinct™ MI300A versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Instinct™ MI300X versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Instinct™ MI308X versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Instinct™ MI325X 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 AMD Radeon™ PRO W6000 Series Graphics Products versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ PRO W7000 Series Graphics Products versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ PROV710 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ RX 6000 Series Graphics Products versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
AMD AMD Radeon™ RX 7000 Series Graphics Products 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
Local
Attack complexity
High
Attack requirements
Present
Privileges required
High
User interaction
None
Scope
X
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
None
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
1.8 CVSS 4.0 Low — — psirt@amd.com via NIST National Vulnerability Database
1.8 CVSS 4.0 Low — — AMD via CVE Program (cve.org) e CISA ADP
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/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-1284

Other CVEs with this weakness →

EPSS over time FIRST

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

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · amd/amd radeon™ rx 6000 series graphics products, amd/amd radeon™ rx 7000 series graphics products, amd/amd radeon™ pro
    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 · 1.8
    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× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

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

Related CVEs (same products)

  • CVE-2026-43598 Untrusted Pointer Dereference in AMD AMD Instinct™ MI210 9d
  • 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-2024-36333 Uncontrolled Search Path Element in AMD Radeon Software May 15, 2026
  • CVE-2024-36323 Improper Access Control in AMD AMD Radeon™ RX 7000 Series Graphics Products 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-66660 is "Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a…", rated Low. 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 1.8 describes technical severity. EPSS 0.10% 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.