CVE-2026-0428: AMD Instinct™ MI300A · Improper Validation of Specified Quantity in Input
Affects AMD Instinct™ MI300ASource CVE Database V5
Not known to be exploited · CVSS 1.8 Low.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AMDAMD Instinct™ MI300A | Affected– | Fixed in– |
| AMDAMD Instinct™ MI300X | Affected– | Fixed in– |
| AMDAMD Instinct™ MI308X | Affected– | Fixed in– |
| AMDAMD Instinct™ MI325X | Affected– | Fixed in– |
AI-suggested
Given the requirement for high privileges to exploit this vulnerability, limiting administrative access and following best practices for privileged account management may reduce risk until a patch is available.
Description
CVE-2026-0428 is a low-severity vulnerability in the AMD Instinct™ MI300A related to improper validation of input parameters in the TEE SOC Driver. Specifically, insufficient sanitization of a command (DRV_SOC_CMD_ID_SRIOV_COPY_VF_CHIPLET_REG) allows an attacker with high privileges to write invalid data to a remote Die, which may cause unexpected behavior. The vulnerability has a CVSS 4.0 base score of 1.8, indicating low impact and complexity. There is no vendor-provided patch or official remediation guidance available at this time, and no known exploits in the wild have been reported. The affected product is not a cloud service, so remediation depends on AMD's release of a fix. No geographic targeting is indicated.