SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Retbleed Reloaded: New Exploit Pierces CPU Memory Defenses

Retbleed Reloaded: New Exploit Pierces CPU Memory Defenses

Security researchers have recently demonstrated a significantly improved exploit for the Retbleed CPU vulnerability, highlighting the ongoing risks posed by speculative execution flaws in modern processors. This exploit allows attackers to read arbitrary memory from affected systems, bypassing secur...

Aug 10, 2025By Meghana Raatni3 min read

Security researchers have recently demonstrated a significantly improved exploit for the Retbleed CPU vulnerability, highlighting the ongoing risks posed by speculative execution flaws in modern processors. This exploit allows attackers to read arbitrary memory from affected systems, bypassing security protections and accessing sensitive data.

Root Cause

The Retbleed vulnerability (CVE-2022-29900, CVE-2022-29901) exploits speculative execution mechanisms in modern CPUs, particularly affecting AMD’s Zen and Zen 2 architectures. Originally discovered in 2022 by ETH Zürich researchers, it allows attackers to manipulate branch predictors and use cache covert channels to extract sensitive data from memory locations.

Unlike many CPU vulnerabilities, Retbleed cannot be fixed through microcode updates. It requires software-level mitigations that fundamentally change how the operating system handles branch prediction and context switching, adding complexity to the mitigation efforts.

Impact & Exploit Potential

The enhanced exploit, detailed by Google security researchers, achieves data leakage rates of approximately 13 KB/s with high accuracy. This speed is sufficient for practical attacks, including listing all running processes and virtual machines on a host system and targeting specific sensitive data such as cryptographic keys.

A particularly concerning aspect is the exploit’s ability to function from sandboxed, unprivileged processes, such as those protected by Chrome’s sandbox. This means that even restricted environments designed to contain potentially malicious code are vulnerable. Furthermore, the exploit can breach virtual machine isolation, allowing attackers to access host machine memory from within a compromised VM, impacting cloud computing environments.

Tactics, Techniques, and Procedures (TTPs)

The exploitation of the Retbleed vulnerability involves specific tactics, techniques, and procedures as defined by the MITRE ATT&CK framework:

  • TA0006 – Credential Access: Attackers exploit the vulnerability to access sensitive credentials stored in memory.
  • TA0005 – Defense Evasion: Attackers use obfuscation techniques to evade security controls and successfully exploit the vulnerability.
  • T1003 – Memory Dump: Attackers dump memory to extract sensitive information, such as credentials and cryptographic keys.
  • T1027 – Obfuscated Files or Information: Attackers use various techniques to hide malicious code and data, making detection more difficult.

Mitigation & Recommendations

Mitigating the Retbleed vulnerability presents significant challenges due to the performance impact of available software mitigations. Google Cloud has responded by migrating workloads that execute arbitrary user code away from affected CPU models. They have also implemented stricter sandbox policies and upgraded to VM-based sandboxing systems that are more resistant to CPU-level vulnerabilities.

The Linux kernel includes default mitigations, but their performance impact makes them unsuitable for many high-performance applications. Organizations using affected AMD processors, particularly in cloud and virtualized environments, must carefully balance security requirements against performance impacts when implementing mitigations.

Available mitigations include:

  • jmp2ret mitigation: incurs a 5-6% performance overhead.
  • IBPB (Indirect Branch Prediction Barrier) mitigation: can cause performance degradation of 55-60% in some workloads.

Instantly Fix Risks with Saner Patch Management

Saner patch management is a continuous, automated, and integrated software that instantly fixes risks exploited in the wild. The software supports major operating systems like Windows, Linux, and macOS, as well as 550+ third-party applications.

It also allows you to set up a safe testing area to test patches before deploying them in a primary production environment. Saner patch management additionally supports a patch rollback feature in case of patch failure or a system malfunction.

Experience the fastest and most accurate patching software here.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026