Hide Forgot
An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of instructions (a commonly used performance optimization). There are three primary variants of the issue which differ in the way the speculative execution can be exploited. Variant CVE-2017-5754 relies on the fact that, on impacted microprocessors, during speculative execution of instruction permission faults, exception generation triggered by a faulting access is suppressed until the retirement of the whole instruction block. In a combination with the fact that memory accesses may populate the cache even when the block is being dropped and never committed (executed), an unprivileged local attacker could use this flaw to read privileged (kernel space) memory by conducting targeted cache side-channel attacks. Note: CVE-2017-5754 affects Intel x86-64 microprocessors. AMD x86-64 microprocessors are not affected by this issue.
Acknowledgments: Name: Google Project Zero
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1530826]
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.2 Advanced Update Support Red Hat Enterprise Linux 7.2 Update Services for SAP Solutions Red Hat Enterprise Linux 7.2 Telco Extended Update Support Via RHSA-2018:0010 https://access.redhat.com/errata/RHSA-2018:0010
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.3 Extended Update Support Via RHSA-2018:0009 https://access.redhat.com/errata/RHSA-2018:0009
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.7 Extended Update Support Via RHSA-2018:0011 https://access.redhat.com/errata/RHSA-2018:0011
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0007 https://access.redhat.com/errata/RHSA-2018:0007
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2018:0008 https://access.redhat.com/errata/RHSA-2018:0008
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0016 https://access.redhat.com/errata/RHSA-2018:0016
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.6 Advanced Update Support Red Hat Enterprise Linux 6.6 Telco Extended Update Support Via RHSA-2018:0017 https://access.redhat.com/errata/RHSA-2018:0017
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.4 Advanced Update Support Via RHSA-2018:0018 https://access.redhat.com/errata/RHSA-2018:0018
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.2 Advanced Update Support Via RHSA-2018:0020 https://access.redhat.com/errata/RHSA-2018:0020
This issue has been addressed in the following products: Red Hat Enterprise MRG 2 Via RHSA-2018:0021 https://access.redhat.com/errata/RHSA-2018:0021
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.5 Advanced Update Support Via RHSA-2018:0022 https://access.redhat.com/errata/RHSA-2018:0022
This issue is fixed for Fedora with the kernel-4.14.11 stable updates.
This issue has been addressed in the following products: RHEV 3.X Hypervisor and Agents for RHEL-6 RHEV 3.X Hypervisor and Agents for RHEL-7 ELS Via RHSA-2018:0046 https://access.redhat.com/errata/RHSA-2018:0046
This issue has been addressed in the following products: RHEV 4.X RHEV-H and Agents for RHEL-7 Via RHSA-2018:0047 https://access.redhat.com/errata/RHSA-2018:0047
This issue has been addressed in the following products: RHEV 3.X Hypervisor and Agents for RHEL-7 Via RHSA-2018:0044 https://access.redhat.com/errata/RHSA-2018:0044
This issue has been addressed in the following products: RHEV 4.X RHEV-H and Agents for RHEL-7 Via RHSA-2018:0045 https://access.redhat.com/errata/RHSA-2018:0045
This issue has been addressed in the following products: CloudForms Management Engine 4.1 Via RHSA-2018:0089 https://access.redhat.com/errata/RHSA-2018:0089
This issue has been addressed in the following products: CloudForms Management Engine 4.2 Via RHSA-2018:0090 https://access.redhat.com/errata/RHSA-2018:0090
This issue has been addressed in the following products: CloudForms Management Engine 4.5 Via RHSA-2018:0091 https://access.redhat.com/errata/RHSA-2018:0091
This issue has been addressed in the following products: CloudForms Management Engine 5.5 Via RHSA-2018:0092 https://access.redhat.com/errata/RHSA-2018:0092
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0151 https://access.redhat.com/errata/RHSA-2018:0151
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.3 Extended Update Support Via RHSA-2018:0182 https://access.redhat.com/errata/RHSA-2018:0182
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Extended Lifecycle Support Via RHSA-2018:0292 https://access.redhat.com/errata/RHSA-2018:0292
This issue has been addressed in the following products: Red Hat Enterprise Linux 5.9 Long Life Via RHSA-2018:0464 https://access.redhat.com/errata/RHSA-2018:0464
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.7 Extended Update Support Via RHSA-2018:0496 https://access.redhat.com/errata/RHSA-2018:0496
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0502 https://access.redhat.com/errata/RHSA-2018:0502
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2018:0512 https://access.redhat.com/errata/RHSA-2018:0512
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0654 https://access.redhat.com/errata/RHSA-2018:0654
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:1062 https://access.redhat.com/errata/RHSA-2018:1062
This issue has been addressed in the following products: Red Hat Enterprise Linux 7.3 Extended Update Support Via RHSA-2018:1129 https://access.redhat.com/errata/RHSA-2018:1129
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2018:1319 https://access.redhat.com/errata/RHSA-2018:1319
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.7 Extended Update Support Via RHSA-2018:1346 https://access.redhat.com/errata/RHSA-2018:1346
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.4 Advanced Update Support Via RHSA-2018:1349 https://access.redhat.com/errata/RHSA-2018:1349
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.6 Advanced Update Support Red Hat Enterprise Linux 6.6 Telco Extended Update Support Via RHSA-2018:1351 https://access.redhat.com/errata/RHSA-2018:1351
This issue has been addressed in the following products: Red Hat Enterprise Linux 6.5 Advanced Update Support Via RHSA-2018:1350 https://access.redhat.com/errata/RHSA-2018:1350
This issue has been addressed in the following products: Red Hat Virtualization Engine 4.3 Via RHSA-2019:1046 https://access.redhat.com/errata/RHSA-2019:1046
Statement: Please see the Vulnerability Response article for the full list of updates available and a detailed discussion of this issue. Meltdown patches for 32-bit Red Hat Enterprise Linux 5 ------------------------------------------------------ Red Hat has no current plans to provide mitigations for the Meltdown vulnerability in 32-bit Red Hat Enterprise Linux 5 environments. Following many hours of engineering investigation and analysis, Red Hat has determined that introducing changes to the Red Hat Enterprise Linux 5 environment would destabilize customer deployments and violate our application binary interface (ABI) and kernel ABI commitments to customers who rely on Red Hat Enterprise Linux 5 to be absolutely stable. Although Red Hat has delivered patches to mitigate the Meltdown vulnerability in other supported product offerings, the 32-bit Red Hat Enterprise Linux 5 environment presents unique challenges. The combination of limited address space in 32-bit environments plus the mechanism for passing control from the userspace to kernel and limitations on the stack during this transfer make the projected changes too invasive and disruptive for deployments that require the highest level of system stability. By contrast, 32-bit Meltdown mitigations have been delivered for Red Hat Enterprise Linux 6, where the changes are far less invasive and risky.
External References: https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://spectreattack.com/ https://meltdownattack.com