AMD Security Bulletin AMD-SB-7055, October 2025
Vulnerability Disclosure:
Supermicro is aware of the security issue that may cause the RDSEED instruction to return “0” at a rate inconsistent with randomness while incorrectly signaling success (CF=1), indicating a potential misclassification of failure as success. AMD released mitigations for this vulnerability. This vulnerability affects BIOS in Supermicro H13 and H14 products.
CVE:
- CVE-2025-62626
- Severity: High
Findings:
Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.
Affected products:
Supermicro BIOS in the server H13 and H14 motherboards.
| AMD Motherboard Generation | BIOS Version with Fix |
|---|---|
| H13 – H13SSW – EPYC™ 9004/9005 series | v 3.7a |
| H13 – H13DSH – EPYC 9004/9005 series | v 3.7a |
| H13 – H13DSG-O-CPU – EPYC 9004/9005 series | v 3.8a |
| H13 – H13SST-G/GC – EPYC 9004/9005 series | v 3.5a |
| H13 – H13SSL-N/NC – EPYC 9004/9005 series | v 3.7a |
| H13 – H13SSH – EPYC 9004/9005 series | v 3.7b |
| H13 – H13SSF – EPYC 9004/9005 series | v 3.7a |
| H13 – H13DSG-OM – EPYC 9004/9005 series | v 3.7b |
| H14 – H14DSH – EPYC 9004/9005 series | v 1.7a |
| H14 – H14SST-G – EPYC 9004/9005 series | v 1.7a |
| H14 – H14SST-GE – EPYC 9005 series | v 1.0a |
| H14 – H14DSG-OD – EPYC 9004/9005 series | v 1.7b |
| H14 – H14SHM – EPYC 9005 series | v 1.7a |
| H14 – H14DST-F/FL – EPYC 9005 series | v 1.7a |
| H14 – H14DSG-O-CPU – EPYC 9004/9005 series | v 1.7a |
| H14 – H14SSL-N/NT – EPYC 9005 series | v 1.7a |
| H14 – H14DSG-OM – EPYC 9004/9005 series | v 1.1c |
Workaround:
Please refer to the AMD security bulletin AMD-SB-7055 for the workaround before you implement new BIOS.
Remediation:
- All affected Supermicro motherboard SKUs will require a BIOS update to mitigate this potential vulnerability.
- An updated BIOS firmware had been created to mitigate this potential vulnerability. Supermicro is currently testing and validating affected products. Please check Release Notes for the resolution.