Transient execution CPU vulnerability

Uses your system voice; voice and rate in settings.

Snapshot

≈ 4 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Transient execution CPU vulnerabilities are vulnerabilities in which instructions, most often optimized using speculative execution, are executed temporarily by a microprocessor, without committing their results due to a misprediction or error, resulting in leaking secret data to an unauthorized party. The archetype is Spectre, and transient execution attacks like Spectre belong to the cache-attack category, one of several categories of side-channel attacks. Since January 2018 many different cache-attack vulnerabilities have been identified.

Transient execution CPU vulnerabilities are vulnerabilities in which instructions, most often optimized using speculative execution, are executed temporarily by a microprocessor, without committing their results due to a misprediction or error, resulting in leaking secret data to an unauthorized party. The archetype is Spectre, and transient execution attacks like Spectre belong to the cache-attack category, one of several categories of side-channel attacks. Since January 2018 many different cache-attack vulnerabilities have been identified.

In June 2021, two new vulnerabilities, Speculative Code Store Bypass (SCSB, CVE-2021-0086) and Floating Point Value Injection (FPVI, CVE-2021-0089), affecting all modern x86-64 CPUs both from Intel and AMD were discovered. In order to mitigate them software has to be rewritten and recompiled. ARM CPUs are not affected by SCSB but some certain ARM architectures are affected by FPVI. Also in June 2021, MIT researchers revealed the PACMAN attack on Pointer Authentication Codes (PAC) in ARM v8.3A.

In August 2021 a vulnerability called "Transient Execution of Non-canonical Accesses" affecting certain AMD CPUs was disclosed. It requires the same mitigations as the MDS vulnerability affecting certain Intel CPUs. It was assigned CVE-2020-12965. Since most x86 software is already patched against MDS and this vulnerability has the exact same mitigations, software vendors don't have to address this vulnerability.

In October 2021 for the first time ever a vulnerability similar to Meltdown was disclosed to be affecting all AMD CPUs however the company doesn't think any new mitigations have to be applied and the existing ones are already sufficient. In July 2025, AMD disclosed a new class of speculative execution vulnerabilities known as Transient Scheduler Attacks (TSA), which were discovered by researchers from Microsoft.

The attacks are affecting AMD Zen 3 and Zen 4 microarchitectures, and they exploit microarchitectural timing leaks in CPU scheduler logic—specifically, the forwarding of incorrect data during false completion of speculative loads—to infer sensitive data from other processes or privilege levels. TSA encompasses four vulnerabilities: (TSA-SQ), which leaks data from prior stores; (TSA-L1), which leverages the L1 data cache; , enabling speculative reads of control registers; and , which leaks TSC_AUX register values.

Mitigations include microcode updates, Linux kernel patches ( tsa= tunable), and optional use of the VERW instruction—albeit with potential performance costs. In September 2025, researchers at ETH Zurich disclosed VMScape ( ), a Spectre-BTI-style transient execution attack that exploits incomplete isolation of the branch predictor between guest virtual machines and host user-space hypervisors (notably QEMU under KVM), allowing a malicious guest to influence speculative execution and leak sensitive host memory.

The flaw affects AMD Zen 1–5 and Intel “Coffee Lake” processors, and mitigations include Linux kernel patches that conditionally issue Indirect Branch Prediction Barrier (IBPB) instructions on VMEXITs before returning control to user-space in order to flush predictor state. | rowspan="2" colspan="2" | rowspan="2" | colspan="2" rowspan="3" |- | colspan="2" |Shared Buffers Data Sampling (SBDS) | |- | colspan="2" |Device Register Partial Write (DRPW) | | colspan="4" | |- | rowspan="4" |Branch Type Confusion (BTC) | rowspan="2" | |BTC-NOBR BTC-DIR | rowspan="2" | | colspan="5" rowspan="2" | colspan="2" |- |BTC-IND | colspan="2" |- | rowspan="2" colspan="2" |Retbleed BTC-RET | rowspan="2" | | rowspan="2" colspan="2" | colspan="2" | rowspan="2" | rowspan="2" colspan="2" |- | colspan="2" |- | colspan="3" |Cross-Thread Return Address Predictions | | colspan="5" || colspan="2" |- | colspan="3" |Zenbleed Cross-Process Information Leak | | colspan="6" || |- | colspan="3" |Inception Speculative Return Stack Overflow (SRSO) | | colspan="5" || colspan="2" |- | colspan="3" |Downfall Gather Data Sampling (GDS) | | colspan="5" || colspan="2" |}

Notes

References

Text derived from https://en.wikipedia.org/w/index.php?oldid=1377824231 under CC BY-SA 4.0; modifications have been made.

Sources cited in this revision

22 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.