⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Low · CVSS 1.8

How to Fix CVE-2026-0428: Access Control Bypass in AMD Instinct™ MI300A

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 1.8 - Low
Actively exploited?Not currently listed in CISA KEV
AffectedAMD Instinct™ MI300A - see advisory for affected version ranges
Fixed inBKC 26, ROCm 6.3.1, ROCm 6.4.2, ROCm 6.3.1
Type (CWE)CWE-1284: Improper Validation of Specified Quantity in Input

What is CVE-2026-0428?

CVE-2026-0428 is an access control bypass flaw in AMD Instinct™ MI300A. Authenticated or in some cases unauthenticated requests reach endpoints they should not be allowed to call, exposing administrative functionality or sensitive data. Vendor description: Insufficient parameter sanitization in TEE SOC Driver could allow an attacker to issue a malformed DRV_SOC_CMD_ID_SRIOV_COPY_VF_CHIPLET_REGS to write invalid data to a remote Die, potentially resulting in unexpected behavior.

Why this CVE matters

Access control flaws let an attacker reach endpoints the developers assumed would be reserved for administrators. The impact depends on what those endpoints expose, but for management products the answer is usually configuration changes, log access, or credential reads.

For deployments of AMD Instinct™ MI300A that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

Check your installed AMD Instinct™ MI300A version against the affected ranges in the vendor advisory linked below. If you cannot determine the version, treat the system as potentially affected and apply the patched build.

Open AMD Instinct™ MI300A's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-0428

The fix is to apply the patched build listed in the AMD advisory.

Affected versions confirmed in the CVE record:

Patch via the OS package manager (Linux)


<!-- enrich_agent_2:v1 -->
# 1. Update the package metadata.
sudo apt update                                  # Debian / Ubuntu
sudo dnf check-update                            # RHEL / Rocky / AlmaLinux / Fedora
sudo zypper refresh                              # openSUSE

# 2. Pull the patched version listed in the [vendor advisory](https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6027.html) of AMD Instinct™ MI300A from AMD.
sudo apt install --only-upgrade amd-instinct-mi300a
sudo dnf upgrade amd-instinct-mi300a
sudo zypper update amd-instinct-mi300a

# 3. Restart the affected service so the patched binary is the running binary.
sudo systemctl restart amd-instinct-mi300a || true

# 4. Verify the running version.
amd-instinct-mi300a --version

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6027.html

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-0428 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-0428?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for AMD Instinct™ MI300A run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*