| Summary: | [TRACKER] hw: cpu: speculative execution bounds-check bypass (CVE-2017-5753) | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | GLSAMaker/CVETool Bot <glsamaker> |
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bertrand, capsel+bugzillagentoo, gentoo-bugzilla, georg, github, kfm, pacho, peter.volkov, randy, remy, sergeev917, z23 |
| Priority: | Normal | Keywords: | Tracker |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 643350, 643352, 644026, 644128, 645510 | ||
| Bug Blocks: | 643228 | ||
|
Description
GLSAMaker/CVETool Bot
2018-01-04 01:01:24 UTC
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-5753 triggers the speculative execution by performing a bounds-check bypass. It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory accesses may cause allocation into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire). As a result, an unprivileged attacker could use this flaw to cross the syscall boundary and read privileged memory by conducting targeted cache side-channel attacks. Source: https://bugzilla.redhat.com/show_bug.cgi?id=1519778 External References: https://access.redhat.com/security/vulnerabilities/speculativeexecution https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html https://spectreattack.com/ https://meltdownattack.com Converting into tracker bug, needed for Xen as well. Unable to check for sanity:
> no match for package: x11-drivers/nvidia-drivers-390.12
Unable to check for sanity:
> dependent bug #644026 has errors
Resetting sanity check; package list is empty or all packages are done. Seems to be an obsolete tracker, closing. |
