Loading story…
Researchers published analysis of Slowburn, examining AMD platform configuration blob infrastructure and its firmware-level attack surface. The research focuses on mechanisms used to configure AMD platforms, underscoring the security significance of low-level firmware components that operate before the operating system.
AMD issued security bulletin AMD-SB-7054 for an issue involving incorrect use of the LocateProtocol service from the EFI_BOOT_Services table within an SMI handler. The flaw affects System Management Mode firmware logic; organizations using affected AMD platforms should review AMD’s advisory, identify impacted firmware versions, and apply vendor-provided firmware updates when available.
See affected versions and whether adversaries are exploiting it.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
ptswarm.com
Open sourceptswarm.com
Open sourceamd.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Binarly Research reported that many AMD-based devices remain vulnerable to speculative execution attacks including **Spectre v1**, **Spectre v2**, and **Retbleed** because firmware and hardware mitigations are not being developed, validated, and delivered consistently across the ecosystem. The findings point to a broad firmware attack surface in **UEFI** and **System Management Mode (SMM)**, where weaknesses below the operating system can leave systems exposed even after years of industry attention on side-channel defenses. The research says asynchronous patching across the hardware and firmware supply chain, combined with limited advisory transparency, has left protections uneven throughout device lifecycles. Binarly warned that these foundational hardware security issues persist in modern AMD environments despite broader emphasis on confidential computing, creating conditions in which attackers could still exploit older speculative execution flaws against current systems.
Jun 29, 2026
AMD disclosed the high-severity **SinkClose** processor vulnerability, tracked as `CVE-2023-31315`, affecting a broad range of AMD CPUs manufactured since 2006. The flaw can be exploited by an attacker who already has kernel-level access to manipulate System Management Mode (SMM) configuration, bypass SMM lock protections, and execute arbitrary code at the highly privileged **Ring -2** level. Researchers Enrique Nissim and Krzysztof Okupski of IOActive showed multiple exploitation paths, including abuse of the **TSeg** protection mechanism and access to sensitive data stored in **SMRAM**. AMD directed customers to obtain product-specific **BIOS updates** from their OEM or system vendor as the primary mitigation for affected platforms.
Jul 24, 2026
AMD disclosed vulnerabilities affecting a broad range of processor, graphics, and accelerator products, including **EPYC**, **Ryzen**, **Athlon**, **Threadripper**, **Instinct MI300A**, and **Radeon PRO V620** lines. The issues are tracked through AMD’s processor-vulnerability security resources, including bulletin `AMD-SB-7009`; public advisories did not specify vulnerability types, exploit conditions, or evidence of active exploitation. Organizations should inventory affected AMD-based servers, desktops, mobile systems, embedded devices, workstations, and accelerators, then obtain and deploy the applicable platform-initialization (PI) firmware updates from their OEM or AMD. Administrators should verify that deployed firmware meets AMD’s published minimum non-affected versions; **Radeon PRO V620** customers should contact AMD Customer Engineering for remediation guidance.
Sep 3, 2026