Transient execution CPU vulnerability

Last updated

Transient execution CPU vulnerabilities are vulnerabilities in a computer system in which a speculative execution optimization implemented in a microprocessor is exploited to leak 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.

Contents

Overview

Modern computers are highly parallel devices, composed of components with very different performance characteristics. If an operation (such as a branch) cannot yet be performed because some earlier slow operation (such as a memory read) has not yet completed, a microprocessor may attempt to predict the result of the earlier operation and execute the later operation speculatively, acting as if the prediction was correct. The prediction may be based on recent behavior of the system. When the earlier, slower operation completes, the microprocessor determines whether prediction was correct or incorrect. If it was correct then execution proceeds uninterrupted; if it was incorrect then the microprocessor rolls back the speculatively executed operations and repeats the original instruction with the real result of the slow operation. Specifically, a transient instruction [1] refers to an instruction processed by error by the processor (incriminating the branch predictor in the case of Spectre) which can affect the micro-architectural state of the processor, leaving the architectural state without any trace of its execution.

In terms of the directly visible behavior of the computer it is as if the speculatively executed code "never happened". However, this speculative execution may affect the state of certain components of the microprocessor, such as the cache, and this effect may be discovered by careful monitoring of the timing of subsequent operations.

If an attacker can arrange that the speculatively executed code (which may be directly written by the attacker, or may be a suitable gadget that they have found in the targeted system) operates on secret data that they are unauthorized to access, and has a different effect on the cache for different values of the secret data, they may be able to discover the value of the secret data.

Timeline

2017–2018

Starting in 2017, multiple examples of such vulnerabilities were identified, with publication starting in early 2018.

2021

In March 2021 AMD security researchers discovered that the Predictive Store Forwarding algorithm in Zen 3 CPUs could be used by malicious applications to access data it shouldn't be accessing. [2] According to Phoronix there's little performance impact in disabling the feature. [3]

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. [4] 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. [5]

In August 2021 a vulnerability called "Transient Execution of Non-canonical Accesses" affecting certain AMD CPUs was disclosed. [6] [7] [8] It requires the same mitigations as the MDS vulnerability affecting certain Intel CPUs. [9] 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 [10] [11] 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. [12]

2022

In March 2022, a new variant of the Spectre vulnerability called Branch History Injection was disclosed. [13] [14] It affects certain ARM64 CPUs [15] and the following Intel CPU families: Cascade Lake, Ice Lake, Tiger Lake and Alder Lake. According to Linux kernel developers AMD CPUs are also affected. [16]

In March 2022, a vulnerability affecting a wide range of AMD CPUs was disclosed under CVE-2021-26341. [17] [18]

In June 2022, multiple MMIO Intel CPUs vulnerabilities related to execution in virtual environments were announced. [19] The following CVEs were designated: CVE-2022-21123, CVE-2022-21125, CVE-2022-21166.

In July 2022, the Retbleed vulnerability was disclosed affecting Intel Core 6 to 8th generation CPUs and AMD Zen 1, 1+ and 2 generation CPUs. Newer Intel microarchitectures as well as AMD starting with Zen 3 are not affected. The mitigations for the vulnerability decrease the performance of the affected Intel CPUs by up to 39%, while AMD CPUs lose up to 14%.

In August 2022, the SQUIP vulnerability was disclosed affecting Ryzen 2000–5000 series CPUs. [20] According to AMD the existing mitigations are enough to protect from it. [21]

According to a Phoronix review released in October, 2022 Zen 4/Ryzen 7000 CPUs are not slowed down by mitigations, in fact disabling them leads to a performance loss. [22] [23]

2023

In February 2023 a vulnerability affecting a wide range of AMD CPU architectures called "Cross-Thread Return Address Predictions" was disclosed. [24] [25] [26]

In July 2023 a critical vulnerability in the Zen 2 AMD microarchitecture called Zenbleed was made public. [27] AMD released a microcode update to fix it. [28]

In August 2023 a vulnerability in AMD's Zen 1, Zen 2, Zen 3, and Zen 4 microarchitectures called Inception [29] [30] was revealed and assigned CVE-2023-20569. According to AMD it is not practical but the company will release a microcode update for the affected products.

Also in August 2023 a new vulnerability called Downfall or Gather Data Sampling was disclosed, [31] [32] [33] affecting Intel CPU Skylake, Cascade Lake, Cooper Lake, Ice Lake, Tiger Lake, Amber Lake, Kaby Lake, Coffee Lake, Whiskey Lake, Comet Lake & Rocket Lake CPU families. Intel will release a microcode update for affected products.

The SLAM [34] [35] [36] [37] vulnerability (Spectre based on Linear Address Masking) reported in 2023 neither has received a corresponding CVE, nor has been confirmed or mitigated against.

2024

In March 2024, a variant of Spectre-V1 attack called GhostRace was published. [38] It was claimed it affected all the major microarchitectures and vendors, including Intel, AMD and ARM. It was assigned CVE-2024-2193. AMD dismissed the vulnerability (calling it "Speculative Race Conditions (SRCs)") claiming that existing mitigations were enough. [39] Linux kernel developers chose not to add mitigations citing performance concerns. [40] The Xen hypervisor project released patches to mitigate the vulnerability but it's not enabled by default. [41]

Also in March 2024, a vulnerability in Intel Atom processors called Register File Data Sampling (RFDS) was revealed. [42] It was assigned CVE-2023-28746. Its mitigations incur a slight performance degradation. [43]

In April 2024, it was revealed that the BHI vulnerability in certain Intel CPU families could be still exploited in Linux entirely in user space without using any kernel features or root access despite existing mitigations. [44] [45] [46] Intel recommended "additional software hardening". [47] The attack was assigned a new CVE-2024-2201.

Future

Spectre class vulnerabilities will remain unfixed because otherwise CPU designers will have to disable speculative execution which will entail a massive performance loss.[ citation needed ] Despite this, AMD has managed to design Zen 4 such a way its performance is not affected by mitigations. [22] [23]

Vulnerabilities and mitigations summary

Mitigation TypeComprehensivenessEffectivenessPerformance Impact
HardwareFullFullNone...Small
MicrocodePartial...FullPartial...FullNone...Large
OS/VMMPartialPartial...FullSmall...Large
Software RecompilationPoorPartial...FullMedium...Large

Hardware mitigations require changes to the CPU design and thus a new iteration of hardware, but impose close to zero performance loss.
Microcode updates alter the software that the CPU runs on which requires patches to be released for each affected CPU and integrated into every BIOS / operating system.
OS/VMM mitigations are applied at the operating system or virtual machine level and (depending on workload) often incur quite a significant performance loss.
Software recompilation requires recompiling lots of pieces of software and usually incurs a severe performance hit.

Vulnerability Name(s)/Subname
Official Name/Subname		CVEAffected CPU architectures and mitigations
Intel [48] AMD [49]
10th gen9th gen8th gen* Zen / Zen+ Zen 2 [50]
Ice Lake [51] Cascade/Comet/
Amber Lake 		Coffee Lake [52] Whiskey Lake Coffee Lake,
Amber Lake
Spectre v1
Bounds Check Bypass		 2017-5753 Software Recompilation [53]
v2
Branch Target Injection [54] 		2017-5715 Hardware + OS/VMM /
Software Recompilation		Microcode + ...Microcode + OS/VMM /
Software Recompilation		Hardware + OS/VMM /
Software Recompilation
Hardware + ... [lower-alpha 1]
Meltdown / v3
Rogue Data Cache Load		 2017-5754 HardwareOSNot affected
Spectre-NGv3a
Rogue System Register Read		 2018-3640 HardwareHardwareMicrocodeMicrocodeMicrocode
Microcode [lower-alpha 2] Hardware [lower-alpha 1]
v4
Speculative Store Bypass [55] 		2018-3639 [Hardware + OS / ]
Software Recompilation		...[Microcode + OS / ]
Software Recompilation		OS/VMMHardware + OS/VMM
... [lower-alpha 1]
Lazy FP State Restore 2018-3665 OS/VMM [56] Not affected
v1.1
Bounds Check Bypass Store		 2018-3693 Software Recompilation [57]
SpectreRSB [58] /ret2spec [59]
Return Mispredict		 2018-15572 OS [60]
Foreshadow
L1 Terminal Fault (L1TF) [61] 		SGX 2018-3615 Not affectedMicrocodeNot affected
OS/SMM 2018-3620 Microcode + OS/VMM
VMM 2018-3646
Microarchitectural Data Sampling (MDS) [62] [63] RIDLZombieLoad
Fill Buffer (MFBDS)		 2018-12130 Microcode + OS
Load Port (MLPDS) 2018-12127 HardwareMicrocode + OS/VMM [lower-alpha 3]
Hardware [lower-alpha 1]
Fallout
Store Buffer (MSBDS)		 2018-12126 Hardware + Microcode [64] [65] Microcode + OS/VMM [lower-alpha 3] Microcode + OS/VMM
Hardware [lower-alpha 1]
RIDLUncacheable Memory (MDSUM) 2019-11091 Same as the buffer having entries
SWAPGS [66] [67] [68] 2019-1125 OS
RIDL
(Rogue In-Flight Data Load)		ZombieLoad v2 [69] [70]
TSX Asynchronous Abort (TAA) [71] [72] 		2019-11135 Hardware [lower-alpha 4] Microcode + OS/VMMExisting MDS mitigationsExisting MDS mitigations
TSX not supported [lower-alpha 2] Microcode + OS/VMM [lower-alpha 1]
ZombieLoad/CacheOut
L1D Eviction Sampling (L1DES) [73] [74] [75] 		2020-0549 Not affectedMicrocodeMicrocode
Not affected [lower-alpha 2]
Vector Register Sampling (VRS) [74] [75] 2020-0548 Microcode
Not affected [lower-alpha 2]
Load Value Injection (LVI) [76] [77] [78] [79] 2020-0551 Software Recompilation (mainly for Intel SGX)
CROSSTalk [80]
Special Register Buffer Data Sampling (SRBDS) [81] 		2020-0543 Microcode [lower-alpha 5] Microcode
Not affected
Branch History Injection (BHI) [82]
and other forms of intra-mode BTI		 2022-0001
 
-0002 		Software RecompilationNot affectedNot affected
Software Recompilation [lower-alpha 1]
MMIO Stale Data [83] Shared Buffers Data Read (SBDR)
Shared Buffers Data Sampling (SBDS)		 2022-21123
2022-21125 		Not affected [lower-alpha 6] Microcode + Software RecompilationSoftware RecompilationNot affected
Microcode + Software Recompilation [lower-alpha 7]
Device Register Partial Write (DRPW) 2022-21166 MicrocodeExisting MDS mitigations
Branch Type Confusion (BTC) [84] Phantom [85] BTC-NOBR
BTC-DIR		 2022-23825 Not affectedOS/VMM
BTC-INDExisting Spectre v2 mitigations
Retbleed [86] [87] [88] [89]
BTC-RET		 2022-29900
 
-29901 		Not affectedOS/VMMOS/VMMOS/VMM /
Software Recompilation
Not affected [lower-alpha 1]
Cross-Thread Return Address Predictions [25] [24] 2022-27672 Not affectedOS/VMM
Zenbleed [90]
Cross-Process Information Leak [91] [92] 		2023-20593 Not affectedMicrocode
Inception [85] [29] [93]
Speculative Return Stack Overflow (SRSO)		 2023-20569 Not affectedOS/VMM
Downfall [32] [33]
Gather Data Sampling (GDS) [31] 		2022-40982 MicrocodeNot affected

The 8th generation Coffee Lake architecture in this table also applies to a wide range of previously released Intel CPUs, not limited to the architectures based on Intel Core, Pentium 4 and Intel Atom starting with Silvermont. [94] [95] Various CPU microarchitectures not included above are also affected, among them are ARM, IBM Power, MIPS and others. [96] [97] [98] [99]

Notes

  1. 1 2 3 4 5 6 7 8 Whiskey Lake stepping C [48]
    Coffee Lake stepping D
  2. 1 2 3 4 Comet Lake except U42 (CPUID 806EC) [48]
  3. 1 2 Cascade Lake stepping 5 [62]
  4. ↑ Ice Lake Xeon-SP (CPUID 606A*) [48]
  5. ↑ Comet Lake U42
    Amber Lake     (CPUID 806EC) [48]
  6. ↑ Cascade Lake [48]
  7. ↑ Ice Lake Core family (CPUID 706E5) [48]

Related Research Articles

RDRAND is an instruction for returning random numbers from an Intel on-chip hardware random number generator which has been seeded by an on-chip entropy source. It is also known as Intel Secure Key Technology, codenamed Bull Mountain. Intel introduced the feature around 2012, and AMD added support for the instruction in June 2015.

In computer security, virtual machine escape is the process of a program breaking out of the virtual machine on which it is running and interacting with the host operating system. A virtual machine is a "completely isolated guest operating system installation within a normal host operating system". In 2008, a vulnerability in VMware discovered by Core Security Technologies made VM escape possible on VMware Workstation 6.0.2 and 5.5.4. A fully working exploit labeled Cloudburst was developed by Immunity Inc. for Immunity CANVAS. Cloudburst was presented in Black Hat USA 2009.

<span class="mw-page-title-main">Intel Management Engine</span> Autonomous computer subsystem

The Intel Management Engine (ME), also known as the Intel Manageability Engine, is an autonomous subsystem that has been incorporated in virtually all of Intel's processor chipsets since 2008. It is located in the Platform Controller Hub of modern Intel motherboards.

Row hammer is a computer security exploit that takes advantage of an unintended and undesirable side effect in dynamic random-access memory (DRAM) in which memory cells interact electrically between themselves by leaking their charges, possibly changing the contents of nearby memory rows that were not addressed in the original memory access. This circumvention of the isolation between DRAM memory cells results from the high cell density in modern DRAM, and can be triggered by specially crafted memory access patterns that rapidly activate the same memory rows numerous times.

Intel Software Guard Extensions (SGX) is a set of instruction codes implementing trusted execution environment that are built into some Intel central processing units (CPUs). They allow user-level and operating system code to define protected private regions of memory, called enclaves. SGX is designed to be useful for implementing secure remote computation, secure web browsing, and digital rights management (DRM). Other applications include concealment of proprietary algorithms and of encryption keys.

<span class="mw-page-title-main">Zen 2</span> 2019 AMD 7-nanometre processor microarchitecture

Zen 2 is a computer processor microarchitecture by AMD. It is the successor of AMD's Zen and Zen+ microarchitectures, and is fabricated on the 7 nm MOSFET node from TSMC. The microarchitecture powers the third generation of Ryzen processors, known as Ryzen 3000 for the mainstream desktop chips, Ryzen 4000U/H and Ryzen 5000U for mobile applications, as Threadripper 3000 for high-end desktop systems, and as Ryzen 4000G for accelerated processing units (APUs). The Ryzen 3000 series CPUs were released on 7 July 2019, while the Zen 2-based Epyc server CPUs were released on 7 August 2019. An additional chip, the Ryzen 9 3950X, was released in November 2019.

<span class="mw-page-title-main">Ryzen</span> AMD brand for microprocessors

Ryzen is a brand of multi-core x86-64 microprocessors designed and marketed by Advanced Micro Devices (AMD) for desktop, mobile, server, and embedded platforms based on the Zen microarchitecture. It consists of central processing units (CPUs) marketed for mainstream, enthusiast, server, and workstation segments and accelerated processing units (APUs) marketed for mainstream and entry-level segments and embedded systems applications.

<span class="mw-page-title-main">Kernel page-table isolation</span>

Kernel page-table isolation is a Linux kernel feature that mitigates the Meltdown security vulnerability and improves kernel hardening against attempts to bypass kernel address space layout randomization (KASLR). It works by better isolating user space and kernel space memory. KPTI was merged into Linux kernel version 4.15, and backported to Linux kernels 4.14.11, 4.9.75, and 4.4.110. Windows and macOS released similar updates. KPTI does not address the related Spectre vulnerability.

<span class="mw-page-title-main">Meltdown (security vulnerability)</span> Microprocessor security vulnerability

Meltdown is one of the two original transient execution CPU vulnerabilities. Meltdown affects Intel x86 microprocessors, IBM POWER processors, and some ARM-based microprocessors. It allows a rogue process to read all memory, even when it is not authorized to do so.

<span class="mw-page-title-main">Spectre (security vulnerability)</span> Processor security vulnerability

Spectre is one of the two original transient execution CPU vulnerabilities, which involve microarchitectural timing side-channel attacks. These affect modern microprocessors that perform branch prediction and other forms of speculation. On most processors, the speculative execution resulting from a branch misprediction may leave observable side effects that may reveal private data to attackers. For example, if the pattern of memory accesses performed by such speculative execution depends on private data, the resulting state of the data cache constitutes a side channel through which an attacker may be able to extract information about the private data using a timing attack.

Speculative Store Bypass (SSB) is the name given to a hardware security vulnerability and its exploitation that takes advantage of speculative execution in a similar way to the Meltdown and Spectre security vulnerabilities. It affects the ARM, AMD and Intel families of processors. It was discovered by researchers at Microsoft Security Response Center and Google Project Zero (GPZ). After being leaked on 3 May 2018 as part of a group of eight additional Spectre-class flaws provisionally named Spectre-NG, it was first disclosed to the public as "Variant 4" on 21 May 2018, alongside a related speculative execution vulnerability designated "Variant 3a".

Lazy FPU state leak, also referred to as Lazy FP State Restore or LazyFP, is a security vulnerability affecting Intel Core CPUs. The vulnerability is caused by a combination of flaws in the speculative execution technology present within the affected CPUs and how certain operating systems handle context switching on the floating point unit (FPU). By exploiting this vulnerability, a local process can leak the content of the FPU registers that belong to another process. This vulnerability is related to the Spectre and Meltdown vulnerabilities that were publicly disclosed in January 2018.

<span class="mw-page-title-main">Foreshadow</span> Hardware vulnerability for Intel processors

Foreshadow, known as L1 Terminal Fault (L1TF) by Intel, is a vulnerability that affects modern microprocessors that was first discovered by two independent teams of researchers in January 2018, but was first disclosed to the public on 14 August 2018. The vulnerability is a speculative execution attack on Intel processors that may result in the disclosure of sensitive information stored in personal computers and third-party clouds. There are two versions: the first version (original/Foreshadow) targets data from SGX enclaves; and the second version (next-generation/Foreshadow-NG) targets virtual machines (VMs), hypervisors (VMM), operating systems (OS) kernel memory, and System Management Mode (SMM) memory. A listing of affected Intel hardware has been posted.

Spoiler is a security vulnerability on modern computer central processing units that use speculative execution. It exploits side-effects of speculative execution to improve the efficiency of Rowhammer and other related memory and cache attacks. According to reports, all modern Intel Core CPUs are vulnerable to the attack as of 2019. AMD has stated that its processors are not vulnerable.

<span class="mw-page-title-main">Microarchitectural Data Sampling</span> CPU vulnerabilities

The Microarchitectural Data Sampling (MDS) vulnerabilities are a set of weaknesses in Intel x86 microprocessors that use hyper-threading, and leak data across protection boundaries that are architecturally supposed to be secure. The attacks exploiting the vulnerabilities have been labeled Fallout, RIDL, ZombieLoad., and ZombieLoad 2.

SWAPGS, also known as Spectre variant 1, is a computer security vulnerability that utilizes the branch prediction used in modern microprocessors. Most processors use a form of speculative execution, this feature allows the processors to make educated guesses about the instructions that will most likely need to be executed in the near future. This speculation can leave traces in the cache, which attackers use to extract data using a timing attack, similar to side-channel exploitation of Spectre.

<span class="mw-page-title-main">Load value injection</span> Microprocessor security vulnerability

Load value injection (LVI) is an attack on Intel microprocessors that can be used to attack Intel's Software Guard Extensions (SGX) technology. It is a development of the previously known Meltdown security vulnerability. Unlike Meltdown, which can only read hidden data, LVI can inject data values, and is resistant to the countermeasures so far used to mitigate the Meltdown vulnerability.

<span class="mw-page-title-main">Hertzbleed</span>

Hertzbleed is a hardware security attack which describes exploiting dynamic frequency scaling to reveal secret data. The attack is a kind of timing attack, bearing similarity to previous power analysis vulnerabilities. Hertzbleed is more dangerous than power analysis, as it can be exploited by a remote attacker. Disclosure of cryptographic keys is the main concern regarding the exploit but other uses of the attack have been demonstrated since its initial discovery.

Retbleed is a speculative execution attack on x86-64 and ARM processors, including some recent Intel and AMD chips. First made public in 2022, it is a variant of the Spectre vulnerability which exploits retpoline, which was a mitigation for speculative execution attacks.

Downfall, known as Gather Data Sampling (GDS) by Intel, is a computer security vulnerability found in 6th through 11th generations of consumer and 1st through 4th generations of Xeon Intel x86-64 microprocessors. It is a transient execution CPU vulnerability which relies on speculative execution of Advanced Vector Extensions (AVX) instructions to reveal the content of vector registers.

References

  1. ↑ Kocher, Paul; Horn, Jann; Fogh, Anders; Genkin, Daniel; Gruss, Daniel. "Spectre Attacks: Exploiting Speculative Execution" (PDF). Retrieved 2020-04-16.
  2. ↑ Cutress, Ian. "AMD Issues Updated Speculative Spectre Security Status: Predictive Store Forwarding". www.anandtech.com. Retrieved 2021-04-08.
  3. ↑ "Benchmarking AMD Zen 3 With Predictive Store Forwarding Disabled - Phoronix". www.phoronix.com. Retrieved 2021-04-08.
  4. ↑ "Rage Against the Machine Clear". VUSec. Retrieved 2021-06-29.
  5. ↑ "Speculative Processor Vulnerability | Frequently asked questions". Arm Developer. Retrieved 2021-06-29.
  6. ↑ "Transient Execution of Non-canonical Accesses".
  7. ↑ Musaev, Saidgani; Fetzer, Christof (2021). "Transient Execution of Non-Canonical Accesses". arXiv: 2108.10771 [cs.CR].
  8. ↑ Francisco, Thomas Claburn in San. "Boffins find if you torture AMD Zen+, Zen 2 CPUs enough, they are vulnerable to Meltdown-like attack". www.theregister.com. Retrieved 2021-09-05.
  9. ↑ https://developer.amd.com/wp-content/resources/90343-D_SoftwareTechniquesforManagingSpeculation_WP_9-20Update_R2.pdf [ bare URL PDF ]
  10. ↑ Lipp, Moritz; Gruss, Daniel; Schwarz, Michael (2021-10-19). "AMD Prefetch Attacks through Power and Time". USENIX Security Symposium.
  11. ↑ "AMD Prefetch Attacks through Power and Time" (PDF).
  12. ↑ "Side-channels Related to the x86 PREFETCH Instruction".
  13. ↑ "Branch History Injection". VUSec. Retrieved 2022-03-08.
  14. ↑ "BHI: The Newest Spectre Vulnerability Affecting Intel & Arm CPUs". www.phoronix.com. Retrieved 2022-03-08.
  15. ↑ Ltd, Arm. "Speculative Processor Vulnerability | Spectre-BHB". Arm Developer. Retrieved 2022-03-11.
  16. ↑ "Linux Lands Mitigations For Spectre-BHB / BHI On Intel & Arm, Plus An AMD Change Too". www.phoronix.com. Retrieved 2022-03-08.
  17. ↑ "grsecurity - The AMD Branch (Mis)predictor Part 2: Where No CPU has Gone Before (CVE-2021-26341)". grsecurity.net. Retrieved 2022-03-11.
  18. ↑ "AMD CPUs May Transiently Execute Beyond Unconditional Direct Branch".
  19. ↑ "oss-security - Xen Security Advisory 404 v2 (CVE-2022-21123,CVE-2022-21125,CVE-2022-21166) - x86: MMIO Stale Data vulnerabilities". www.openwall.com. Retrieved 2022-06-19.
  20. ↑ "AMD Details "SQUIP" Side Channel Vulnerability For Zen's Execution Unit Scheduler". www.phoronix.com. Retrieved 2022-08-10.
  21. ↑ "Execution Unit Scheduler Contention Side-Channel Vulnerability on AMD Processors".
  22. 1 2 "With AMD Zen 4, It's Surprisingly Not Worthwhile Disabling CPU Security Mitigations". www.phoronix.com. Retrieved 2022-10-07.
  23. 1 2 "Disabling Spectre V2 Mitigations Is What Can Impair AMD Ryzen 7000 Series Performance". www.phoronix.com. Retrieved 2022-10-07.
  24. 1 2 "[FYI PATCH 0/3] Cross-Thread Return Address Predictions vulnerability [LWN.net]". lwn.net. Retrieved 2023-02-14.
  25. 1 2 "Cross-Thread Return Address Predictions | AMD". February 14, 2022. Retrieved 2023-08-11.
  26. ↑ "oss-sec: Xen Security Advisory 426 v1 (CVE-2022-27672) - x86: Cross-Thread Return Address Predictions". seclists.org. Retrieved 2023-02-15.
  27. ↑ Paul Alcorn (2023-07-24). "AMD 'Zenbleed' Bug Allows Data Theft From Zen 2 Processors, Patches Coming". Tom's Hardware. Retrieved 2023-07-24.
  28. ↑ "Cross-Process Information Leak". amd.com. 2023-07-24. Retrieved 2023-07-27.
  29. 1 2 "Return Address Security Bulletin". amd.com. 2023-08-08. Retrieved 2023-08-08.
  30. ↑ "New Inception attack leaks sensitive data from all AMD Zen CPUs". BleepingComputer. Retrieved 2023-08-09.
  31. 1 2 "Gather Data Sampling". Intel. Retrieved 2023-08-09.
  32. 1 2 "Downfall". Downfall Attacks. Retrieved 2023-08-09.
  33. 1 2 "Downfall and Zenbleed: Googlers helping secure the ecosystem". Google Online Security Blog. Retrieved 2023-08-09.
  34. ↑ "SLAM: Spectre based on Linear Address Masking". vusec. Retrieved 2023-12-07.
  35. ↑ "TLB-Based Side Channel Attack: Security Update". developer.arm.com. Retrieved 2023-12-07.
  36. ↑ "oss-sec: SLAM: Spectre based on Linear Address Masking". seclists.org. Retrieved 2023-12-07.
  37. ↑ "New SLAM attack steals sensitive data from AMD, future Intel CPUs". BleepingComputer. Retrieved 2023-12-07.
  38. ↑ "GhostRace". vusec. Retrieved 2024-03-12.
  39. ↑ "Speculative Race Conditions (SRCs)". amd.com. 2024-03-12.
  40. ↑ "GhostRace Detailed - Speculative Race Conditions Affecting All Major CPUs / ISAs". www.phoronix.com. Retrieved 2024-03-12.
  41. ↑ "oss-sec: Xen Security Advisory 453 v1 (CVE-2024-2193) - GhostRace: Speculative Race Conditions". seclists.org. Retrieved 2024-03-14.
  42. ↑ "Register File Data Sampling". Intel. Retrieved 2024-03-15.
  43. ↑ "The Performance Impact Of Intel's Register File Data Sampling". www.phoronix.com. Retrieved 2024-03-15.
  44. ↑ "InSpectre Gadget". vusec. Retrieved 2024-04-14.
  45. ↑ "oss-security - Xen Security Advisory 456 v2 (CVE-2024-2201) - x86: Native Branch History Injection". www.openwall.com. Retrieved 2024-04-14.
  46. ↑ "2268118 – (CVE-2024-2201) CVE-2024-2201 hw: cpu: intel:InSpectre Gadget a residual Attack Surface of Cross-privilege Spectre v2". bugzilla.redhat.com. Retrieved 2024-04-14.
  47. ↑ "Branch History Injection and Intra-mode Branch Target Injection". Intel. Retrieved 2024-04-14.
  48. 1 2 3 4 5 6 7 "Affected Processors: Transient Execution Attacks & Related Security Issues by CPU". Intel. November 3, 2023. Archived from the original on 2021-05-09. Retrieved 2024-03-12.
  49. ↑ "AMD Product Security | AMD". August 10, 2019. Retrieved 2019-08-10.
  50. ↑ Cutress, Ian. "AMD Zen 2 Microarchitecture Analysis: Ryzen 3000 and EPYC Rome". www.anandtech.com. Retrieved 2019-06-11.
  51. ↑ Cutress, Dr Ian. "The Ice Lake Benchmark Preview: Inside Intel's 10nm". www.anandtech.com. Retrieved 2019-08-01.
  52. ↑ "Intel Core i9-9900K mit 8 Kernen und 5 GHz für Gamer". heise online (in German). October 8, 2018. Retrieved 2018-10-09.
  53. ↑ https://developer.amd.com/wp-content/resources/90343-B_SoftwareTechniquesforManagingSpeculation_WP_7-18Update_FNL.pdf [ bare URL PDF ]
  54. ↑ Intel (January 3, 2018). Branch Target Injection (Technical report). Retrieved 2024-03-06. Two mitigation techniques have been developed ...: indirect branch control mechanisms and a software approach called ... retpoline
  55. ↑ Intel (May 21, 2018). Speculative Store Bypass (Technical report). Retrieved 2024-03-06. To minimize performance impact, we do not currently recommend setting SSBD for OSes, VMMs
  56. ↑ "INTEL-SA-00145". Intel.
  57. ↑ "Bounds Check Bypass Store (BCBS) Vulnerability (INTEL-OSS-10002)". Intel.
  58. ↑ "Spectre Returns! Speculation Attacks using the Return Stack Buffer" (PDF). www.usenix.org. Retrieved 2019-08-17.
  59. ↑ Maisuradze, Giorgi; Rossow, Christian (2018). "ret2spec: Speculative Execution Using Return Stack Buffers". Proceedings of the 2018 ACM SIGSAC Conference on Computer and Communications Security. pp. 2109–2122. arXiv: 1807.10364 . Bibcode:2018arXiv180710364M. doi:10.1145/3243734.3243761. ISBN   9781450356930. S2CID   51804116.
  60. ↑ "Kernel/Git/Torvalds/Linux.git - Linux kernel source tree".
  61. ↑ "Processors Affected: L1 Terminal Fault". Intel. August 14, 2018. Retrieved 2024-03-06. ...processors that have the RDCL_NO bit set to one (1) ... are not susceptible to the L1TF
  62. 1 2 "Processors Affected: Microarchitectural Data Sampling". Intel. May 14, 2019. Retrieved 2024-03-07. MFBDS is mitigated if either the RDCL_NO or MDS_NO bit ... are set. [...]
    All processors affected by MSBDS, MFBDS, or MLPDS are also affected by MDSUM for the relevant buffers.
  63. ↑ Intel (March 11, 2021) [Disclosed May 14, 2019]. Microarchitectural Data Sampling (Technical report). Retrieved 2024-03-07. VMMs that already ... mitigate L1TF may not need further changes ... a VERW may be needed to overwrite the store buffers
  64. ↑ Moghimi, Daniel (July 14, 2020). Data Sampling on MDS-resistant 10th Generation Intel Core (Ice Lake). GitHub (Technical report). Worcester Polytechnic Institute. Retrieved 2020-07-15.
  65. ↑ Intel (July 14, 2020). "Microarchitectural Data Sampling Advisory" (Press release). Retrieved 2020-07-15. Intel Core Processor Family (Ice Lake)
  66. ↑ "Bitdefender SWAPGS Attack Mitigation Solutions". www.bitdefender.com. Retrieved 2019-08-07.
  67. ↑ "Documentation/admin-guide/hw-vuln/spectre.rst - chromiumos/third_party/kernel - Git at Google". chromium.googlesource.com. Archived from the original on 2019-08-07. Retrieved 2019-08-07.
  68. ↑ Winder, Davey (August 6, 2019). "Microsoft Confirms New Windows CPU Attack Vulnerability, Advises All Users To Update Now". Forbes . Retrieved 2019-08-07.
  69. ↑ at 18:02, Shaun Nichols in San Francisco 12 Nov 2019. "True to its name, Intel CPU flaw ZombieLoad comes shuffling back with new variant". www.theregister.co.uk. Retrieved 2019-11-12.{{cite web}}: CS1 maint: numeric names: authors list (link)
  70. ↑ Cimpanu, Catalin. "Intel's Cascade Lake CPUs impacted by new Zombieload v2 attack". ZDNet. Retrieved 2019-11-12.
  71. ↑ "Cyberus Technology: TSX Asynchronous Abort". www.cyberus-technology.de. Retrieved 2019-11-12.
  72. ↑ Intel (November 12, 2019). Intel TSX Asynchronous Abort (Technical report). Retrieved 2024-03-12. TAA can be mitigated by either applying the MDS software mitigations or by selectively disabling Intel TSX
  73. ↑ "CacheOut". cacheoutattack.com. Retrieved 2020-01-29.
  74. 1 2 "MDS Attacks: Microarchitectural Data Sampling". mdsattacks.com. Retrieved 2020-01-27.
  75. 1 2 "IPAS: INTEL-SA-00329". Technology@Intel. January 27, 2020. Retrieved 2020-01-28.
  76. ↑ "LVI: Hijacking Transient Execution with Load Value Injection". lviattack.eu. Retrieved 2020-03-10.
  77. ↑ "INTEL-SA-00334". Intel. Retrieved 2020-03-10.
  78. ↑ "Deep Dive: Load Value Injection". software.intel.com. Retrieved 2020-03-10.
  79. ↑ at 17:00, Thomas Claburn in San Francisco 10 Mar 2020. "You only LVI twice: Meltdown The Sequel strikes Intel chips – and full mitigation against data-meddling flaw will cost you 50%+ of performance". www.theregister.co.uk. Retrieved 2020-03-10.{{cite web}}: CS1 maint: numeric names: authors list (link)
  80. ↑ "CROSSTalk". VUSec. Retrieved 2020-06-09.
  81. ↑ Intel (June 14, 2022) [Disclosed June 9, 2020]. Special Register Buffer Data Sampling (Technical report). Retrieved 2024-03-21. systems that have loaded the microcode ... are fully mitigated by default
  82. ↑ Intel (March 11, 2022) [Disclosed March 8, 2022]. Branch History Injection and Intra-mode Branch Target Injection (Technical report). Retrieved 2024-03-22. potential BHI attacks can be mitigated by adding LFENCE to specific identified gadgets
  83. ↑ Intel (June 14, 2022). Processor MMIO Stale Data Vulnerabilities (Technical report). Retrieved 2024-04-17. For processors ... where MD_CLEAR may not overwrite fill buffer values, Intel has released microcode updates ... so that VERW does overwrite fill buffer values. [...]
    To mitigate this, the OS, VMM, or driver that reads the secret data can reduce the window in which that data remains vulnerable ... by performing an additional read of some non-secret data
  84. ↑ AMD (July 12, 2022). "AMD CPU Branch Type Confusion" (Press release). Retrieved 2024-03-25.
  85. 1 2 "Inception: how a simple XOR can cause a Microarchitectural Stack Overflow". Computer Security Group. Retrieved 2023-09-15.
  86. ↑ "Retbleed: Arbitrary Speculative Code Execution with Return Instructions – Computer Security Group" . Retrieved 2022-07-12.
  87. ↑ "INTEL-SA-00702". Intel. Retrieved 2022-07-13.
  88. ↑ "AMD, Intel chips vulnerable to 'Retbleed' Spectre variant". www.theregister.com. Retrieved 2022-07-12.
  89. ↑ Goodin, Dan (July 12, 2022). "New working speculative execution attack sends Intel and AMD scrambling". Ars Technica. Retrieved 2022-07-12.
  90. ↑ "security-research/pocs/cpus/zenbleed at master · google/security-research". GitHub. Retrieved 2023-07-27.
  91. ↑ "AMD: Information Leak in Zen 2". GitHub. Retrieved 2023-07-27.
  92. ↑ "Cross-Process Information Leak". AMD. Retrieved 2023-07-27.
  93. ↑ "oss-security - Xen Security Advisory 434 v1 (CVE-2023-20569) - x86/AMD: Speculative Return Stack Overflow". www.openwall.com. Retrieved 2023-09-15.
  94. ↑ "INTEL-SA-00088". Intel. Retrieved 2018-09-01.
  95. ↑ "INTEL-SA-00115". Intel. Retrieved 2018-09-01.
  96. ↑ "Meltdown and Spectre Status Page". wiki.netbsd.org. Retrieved 2019-09-29.
  97. ↑ Ltd, Arm. "Speculative Processor Vulnerability | Cache Speculation Issues Update". ARM Developer. Retrieved 2019-09-29.
  98. ↑ "About speculative execution vulnerabilities in ARM-based and Intel CPUs". Apple Support. May 31, 2018. Retrieved 2019-09-29.
  99. ↑ "Potential Impact on Processors in the POWER Family". IBM PSIRT Blog. May 14, 2019. Retrieved 2019-09-29.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.