Transient execution CPU vulnerability

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.

Main articles: Downfall (security vulnerability), Foreshadow, Lazy FP state restore, Load value injection, Meltdown (security vulnerability), Microarchitectural Data Sampling, Retbleed, Spectre (security vulnerability), Speculative Store Bypass, and SWAPGS (security vulnerability)

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. 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 impactDescription
Hardware FullFullNone to small Require changes to the CPU design and thus a new iteration of hardware
Microcode Partial to fullPartial to fullNone to large Updates the software that the CPU runs on which requires patches to be released for each affected CPU and integrated into every BIOS or operating system
OS/VMM PartialPartial to fullSmall to large Applied at the operating system or virtual machine level and (depending on workload)
Software recompilation PoorPartial to fullMedium to large Requires recompiling lots of pieces of software
Vulnerability Name(s)/Subname
Official Name/Subname		 CVE Affected 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		 CVE-2017-5753 Software recompilation[53]
v2
Branch Target Injection[54]		 CVE-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		 CVE-2017-5754 HardwareOS Not affected
Spectre-NG v3a
Rogue System Register Read		 CVE-2018-3640 Hardware Hardware Microcode Microcode Microcode
Microcode[lower-alpha 2] Hardware[lower-alpha 1]
v4
Speculative Store Bypass[55]		 CVE-2018-3639 [Hardware + OS / ]
Software recompilation		 ... [Microcode + OS / ]
Software recompilation		 OS/VMMHardware + OS/VMM
...[lower-alpha 1]
Lazy FP State Restore CVE-2018-3665 OS/VMM[56] Not affected
v1.1
Bounds Check Bypass Store		 CVE-2018-3693 Software recompilation[57]
SpectreRSB[58]/ret2spec[59]
Return Mispredict		 CVE-2018-15572 OS[60]
Foreshadow
L1 Terminal Fault (L1TF)[61]		 SGX CVE-2018-3615 Not affected Microcode Not affected
OS/SMM CVE-2018-3620 Microcode + OS/VMM
VMM CVE-2018-3646
Microarchitectural Data Sampling (MDS)[62][63] RIDL ZombieLoad
Fill Buffer (MFBDS)		 CVE-2018-12130 Microcode + OS
Load Port (MLPDS) CVE-2018-12127 Hardware Microcode + OS/VMM[lower-alpha 3]
Hardware[lower-alpha 1]
Fallout
Store Buffer (MSBDS)		 CVE-2018-12126 Hardware + Microcode[64][65] Microcode + OS/VMM[lower-alpha 3] Microcode + OS/VMM
Hardware[lower-alpha 1]
RIDLUncacheable Memory (MDSUM) CVE-2019-11091 Same as the buffer having entries
SWAPGS[66][67][68] CVE-2019-1125 OS
RIDL
(Rogue In-Flight Data Load)		 ZombieLoad v2[69][70]
TSX Asynchronous Abort (TAA)[71][72]		 CVE-2019-11135 Hardware[lower-alpha 4] Microcode + OS/VMM Existing MDS mitigations Existing MDS mitigations
TSX not supported[lower-alpha 2] Microcode + OS/VMM[lower-alpha 1]
ZombieLoad/CacheOut
L1D Eviction Sampling (L1DES)[73][74][75]		 CVE-2020-0549 Not affected Microcode Microcode
Not affected[lower-alpha 2]
Vector Register Sampling (VRS)[74][75] CVE-2020-0548 Microcode
Not affected[lower-alpha 2]
Load Value Injection (LVI)[76][77][78][79] CVE-2020-0551 Software recompilation (mainly for Intel SGX)
CROSSTalk[80]
Special Register Buffer Data Sampling (SRBDS)[81]		 CVE-2020-0543 Microcode[lower-alpha 5] Microcode
Not affected
Floating Point Value Injection (FPVI)[82][83] CVE-2021-0086
CVE-2021-26314		 Software recompilation
Speculative Code Store Bypass (SCSB)[84][83] CVE-2021-0089
CVE-2021-26313
Branch History Injection (BHI)[85]
and other forms of intra-mode BTI		 CVE-2022-0001
CVE-2022-0002		 Software recompilation Not affected Not affected
Software recompilation[lower-alpha 1]
MMIO Stale Data[86] Shared Buffers Data Read (SBDR) CVE-2022-21123
Not affected[lower-alpha 6]
Microcode + Software recompilation[lower-alpha 7]
 Microcode + Software recompilation Software recompilation Not affected
Shared Buffers Data Sampling (SBDS) CVE-2022-21125
Device Register Partial Write (DRPW) CVE-2022-21166 Microcode Existing MDS mitigations
Branch Type Confusion (BTC)[87] Phantom[88] BTC-NOBR
BTC-DIR		 CVE-2022-23825 Not affected OS/VMM
BTC-IND Existing Spectre v2 mitigations
Retbleed[89][90][91][92]
BTC-RET		 CVE-2022-29900
CVE-2022-29901		 Not affected OS/VMM OS/VMM OS/VMM /
Software recompilation
Not affected[lower-alpha 1]
Cross-Thread Return Address Predictions[25][24] CVE-2022-27672 Not affectedOS/VMM
Zenbleed[93]
Cross-Process Information Leak[94][95]		 CVE-2023-20593 Not affectedMicrocode
Inception[88][29][96]
Speculative Return Stack Overflow (SRSO)		 CVE-2023-20569 Not affectedOS/VMM
Downfall[32][33]
Gather Data Sampling (GDS)[31]		 CVE-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.[97][98] Various CPU microarchitectures not included above are also affected, among them are ARM, IBM Power, MIPS and others.[99][100][101][102]

Notes
  1. Whiskey Lake stepping C[48]
    Coffee Lake stepping D
  2. Comet Lake except U42 (CPUID 806EC)[48]
  3. 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]

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
  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. "With AMD Zen 4, It's Surprisingly Not Worthwhile Disabling CPU Security Mitigations". www.phoronix.com. Retrieved 2022-10-07.
  23. "Disabling Spectre V2 Mitigations Is What Can Impair AMD Ryzen 7000 Series Performance". www.phoronix.com. Retrieved 2022-10-07.
  24. "[FYI PATCH 0/3] Cross-Thread Return Address Predictions vulnerability [LWN.net]". lwn.net. Retrieved 2023-02-14.
  25. "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. "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. "Gather Data Sampling". Intel. Retrieved 2023-08-09.
  32. "Downfall". Downfall Attacks. Retrieved 2023-08-09.
  33. "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. "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
  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. "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. "MDS Attacks: Microarchitectural Data Sampling". mdsattacks.com. Retrieved 2020-01-27.
  75. "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 (June 8, 2021). Floating Point Value Injection (Technical report). Retrieved 2024-05-03. Managed runtimes impacted by FPVI ...
  83. AMD (June 8, 2021). "Speculative Code Store Bypass and Floating-Point Value Injection" (Press release). Retrieved 2024-05-03.
  84. Intel (June 8, 2021). Speculative Code Store Bypass (Technical report). Retrieved 2024-05-03. For example, some JIT compilers inside web browsers ... may be impacted by SCSB
  85. 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 ...
  86. 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
  87. AMD (July 12, 2022). "AMD CPU Branch Type Confusion" (Press release). Retrieved 2024-03-25.
  88. "Inception: how a simple XOR can cause a Microarchitectural Stack Overflow". Computer Security Group. Retrieved 2023-09-15.
  89. "Retbleed: Arbitrary Speculative Code Execution with Return Instructions – Computer Security Group". Retrieved 2022-07-12.
  90. "INTEL-SA-00702". Intel. Retrieved 2022-07-13.
  91. "AMD, Intel chips vulnerable to 'Retbleed' Spectre variant". www.theregister.com. Retrieved 2022-07-12.
  92. Goodin, Dan (July 12, 2022). "New working speculative execution attack sends Intel and AMD scrambling". Ars Technica. Retrieved 2022-07-12.
  93. "security-research/pocs/cpus/zenbleed at master · google/security-research". GitHub. Retrieved 2023-07-27.
  94. "AMD: Information Leak in Zen 2". GitHub. Retrieved 2023-07-27.
  95. "Cross-Process Information Leak". AMD. Retrieved 2023-07-27.
  96. "oss-security - Xen Security Advisory 434 v1 (CVE-2023-20569) - x86/AMD: Speculative Return Stack Overflow". www.openwall.com. Retrieved 2023-09-15.
  97. "INTEL-SA-00088". Intel. Retrieved 2018-09-01.
  98. "INTEL-SA-00115". Intel. Retrieved 2018-09-01.
  99. "Meltdown and Spectre Status Page". wiki.netbsd.org. Retrieved 2019-09-29.
  100. Ltd, Arm. "Speculative Processor Vulnerability | Cache Speculation Issues Update". ARM Developer. Retrieved 2019-09-29.
  101. "About speculative execution vulnerabilities in ARM-based and Intel CPUs". Apple Support. May 31, 2018. Retrieved 2019-09-29.
  102. "Potential Impact on Processors in the POWER Family". IBM PSIRT Blog. May 14, 2019. Retrieved 2019-09-29.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.