Epstein Files Full PDF

Intel MPX (Memory Protection Extensions) are a discontinued set of extensions to the x86 instruction set architecture. With compiler, runtime library and operating system support, Intel MPX claimed to enhance security to software by checking pointer references whose normal compile-time intentions are maliciously exploited at runtime due to buffer overflows. In practice, there have been too many flaws discovered in the design for it to be useful, and support has been deprecated or removed from most compilers and operating systems. Intel has listed MPX as removed in 2019 and onward hardware in section 2.5 of its Intel® 64 and IA-32 Architectures Software Developer's Manual Volume 1.^[1]

Intel MPX introduces new bounds registers, and new instruction set extensions that operate on these registers. Additionally, there is a new set of "bound tables" that store bounds beyond what can fit in the bounds registers.^{[2][3][4][5][6]}

MPX uses four new 128-bit bounds registers, BND0 to BND3, each storing a pair of 64-bit lower bound (LB) and upper bound (UB) values of a buffer. The upper bound is stored in ones' complement form, with BNDMK (create bounds) and BNDCU (check upper bound) performing the conversion. The architecture includes two configuration registers BNDCFGx (BNDCFGU in user space and BNDCFGS in kernel mode), and a status register BNDSTATUS, which provides a memory address and error code in case of an exception.^[7][8]

Two-level address translation is used for storing bounds in memory. The top layer consists of a Bounds Directory (BD) created on the application startup. Each BD entry is either empty or contains a pointer to a dynamically created Bounds Table (BT), which in turn contains a set of pointer bounds along with the linear addresses of the pointers. The bounds load (BNDLDX) and store (BNDSTX) instructions transparently perform the address translation and access bounds in the proper BT entry.^[7][8]

Intel MPX was introduced as part of the Skylake microarchitecture.^[9]

Intel Goldmont microarchitecture also supports Intel MPX.^[9]

• glibc removed support in version 2.35.
• GNU Compiler Collection (GCC) 5.0 added support for MPX.^[10] In 2018, support for these extensions waned due to maintenance burdens and Intel developers intermittently contributing patches, resulting in a proposal to drop support in GCC 9.0.^[11] Support was removed in GCC 9.1.^[12]
• Intel C++ Compiler (icc) 15.0 added support for Intel MPX.^[10]
• Kernel-level software support for Intel MPX was merged into the Linux kernel mainline in kernel version 3.19, which was released on February 8, 2015.^[13][14] In 2018, Thomas Gleixner proposed removing MPX support from Linux kernel 4.18.^[15] The pull request with its removal was posted in December 2018, during 4.20 development cycle,^[16] but wasn't accepted. The second attempt was made in July 2019.^[17] MPX support was removed in 5.6.^[18]
• QEMU supported MPX since version 2.6^[19] and dropped its support in 4.0 release.^[20]
• Microsoft Visual Studio 2015 Update 1 added experimental support for MPX.^[21]

A study examined a detailed cross-layer dissection of the MPX system stack and comparison with three prominent software-based memory protection mechanisms (AddressSanitizer, SAFECode, and SoftBound) and presents the following conclusions.^[8]

• Even though Intel MPX is a specially designed hardware-assisted approach with its own added set of hardware registers, it is not faster than any of the software-based approaches. New Intel MPX instructions can cause up to 4× slowdown in the worst case, although compiler optimizations amortize it and lead to runtime overheads of ~50% on average.
• In contrast to the other software-based solutions, Intel MPX provides no protection against temporal memory safety errors.
• Reading and writing from the doubly-indirected bounds tables is not thread-safe.
• MPX does not support several common C/C++ programming idioms, such as flexible array members, referencing one field as an offset from another, etc.
• MPX conflicts with some other ISA extensions, resulting in performance and security issues. More specifically, these issues arise when Intel MPX is used in combination with other hardware-based protection mechanisms, such as Intel TSX and Intel SGX.
• MPX instructions incur a significant performance penalty (15+%) even on Intel CPUs without MPX support.

In addition, a review concluded MPX was not production ready, and AddressSanitizer was a better option.^[8] A review by Kostya Serebryany at Google, AddressSanitizer's developer,^[22] had similar findings.^[23]

Another study^[24] exploring the scope of Spectre and Meltdown security vulnerabilities discovered that Meltdown can be used to bypass Intel MPX, using the Bound Range Exceeded (#BR) hardware exception. According to their publication, the researchers were able to leak information through a Flush+Reload covert channel from an out-of-bound access on an array safeguarded by the MPX system. Their Proof Of Concept has not been publicly disclosed.

• Memory protection keys
• Software Guard Extensions

• Intel Architecture Instruction Set Extensions Programming Reference (PDF). Intel. July 2013. Retrieved 2016-01-10.
• Oleksenko, Oleksii; Kuvaiskii, Dmitrii; Bhatotia, Pramod; Felber, Pascal; Fetzer, Christof (2017). "Intel MPX Explained: An Empirical Study of Intel MPX and Software-based Bounds Checking Approaches". arXiv:1702.00719 [cs.CR]. Online supplementary material at https://intel-mpx.github.io.
• "Introduction to Intel Memory Protection Extensions". Intel. 2013-07-16. Retrieved 2013-09-10.
• "Intel ISA Extensions". Intel. Retrieved 2013-11-04.
• "Intel® Memory Protection Extensions (Intel® MPX) support in the GCC compiler". gcc.gnu.org. Retrieved 2013-11-04.
• Hansen, Dave (2016-03-16). "Intel® Memory Protection Extensions (Intel® MPX) for Linux". Retrieved 2018-05-17.