Critical Core Risks Found
Teams must act fast to protect cloud hubs. Experts found major AMD security vulnerabilities that hurt chip safety. Therefore, you must update your systems now. These big hardware security flaws can let bad actors skip security rules. Consequently, keeping tools safe is vital for your firm. You should check your setup today to stop bad attacks and ensure total peace of mind.
Cache Problems Break Safe Checks
The first big issue impacts safe memory tools. Scientists wrote a paper named “Undermining AMD SEV-SNP by Making the PSP Non-coherent.” This text shows how a bad host can trick the chip. By turning off clean cache rules, the system reads old data from memory. Thus, new updates from the guest get lost. This can harm data truth and break vital safety goals for cloud tenants. This flaw is tracked as CVE-2025-54509 and has a CVSS score of 4.0.
Impact on EPYC Chip Systems
This bug impacts many fast chips. Reports say that “analysis by AMD is that this issue impacts 4th and 5th generation EPYC platforms.” Exploiting this flaw needs a bad host system. Furthermore, real attacks depend on a tight race condition. This means bad actors need perfect timing to steal data. If they fail, the system stays completely safe from harm.
To help users, the firm released new platform code. You can see the full list on the main AMD SB-3039 advisory web page. Specifically, users of these modern chips must change their BIOS code. Fortunately, builders already have these fixes ready. Therefore, you should call your vendor to get the new patch today without any delay.
ARM Translation Flaws Impact Special Hardware
The second risk impacts a different chip part. A bad memory lookup flaw hurts some fast chips. Experts state that “completion of affected memory accesses might not be guaranteed by completion of a Translation Lookaside Buffer Invalidate.” Consequently, a bad actor can skip key translation steps. This bad action lets untrusted code run on the host. This flaw is tracked as CVE-2025-10263 and has a CVSS score of 9.1.
Firmware Mitigations Ready
Fortunately, simple code fixes exist for this problem. Devs put a clear fix in the main firmware library. You can read the whole note on the AMD SB-8021 advisory page. Additionally, teams plan to push new Linux patches to fix the bug. The firm will add these fixes to their board package soon.
Quick Steps for Tech Teams
Firms must act now to block these hardware security flaws. First, check your current system versions. Second, test the new patches in a safe room. Finally, push the clean BIOS updates to your real servers. Doing this keeps your guest data safe from big risks. Do not wait to fix your code. Keep your network safe from all potential digital threats.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.