# CVE-2017-5753: Information disclosure in Most Modern Operating Systems > Local attackers can exploit speculative execution side-channels to read unauthorized memory, affecting most modern operating systems. - **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Jan 2018 - **Updated:** 28 May 2026 - **Also known as:** ALPINE-CVE-2017-5753, DEBIAN-CVE-2017-5753, RHSA-2018:0182, RHSA-2018:0496, RHSA-2018:0512, SUSE-SU-2021:2861-1, SUSE-SU-2021:2862-1, UBUNTU-CVE-2017-5753, USN-3521-1, openSUSE-SU-2021:1212-1, openSUSE-SU-2021:2861-1 ## What is CVE-2017-5753? CVE-2017-5753 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 4 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis. Weakness: CWE-203 (Observable Discrepancy) ## Which versions are affected by CVE-2017-5753? It affects 308 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-696.23.1.el6 | | `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-headers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-696.23.1.el6 | | `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | | `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-696.23.1.el6 | Products: Arm Cortex-A12 Firmware, Arm Cortex-A15 Firmware, Arm Cortex-A17 Firmware, Arm Cortex-A57 Firmware, Arm Cortex-A72 Firmware, Arm Cortex-A73 Firmware, Arm Cortex-A75 Firmware, Arm Cortex-A76 Firmware, Arm Cortex-A77 Firmware, Arm Cortex-A78 Firmware, Arm Cortex-A78ae Firmware, Arm Cortex-A8 Firmware, Arm Cortex-A9 Firmware, Arm Cortex-R7 Firmware, Arm Cortex-R8 Firmware, Arm Cortex-X1 Firmware, Arm Neoverse N1 Firmware, Arm Neoverse N2 Firmware, Canonical Ubuntu Linux, Debian Debian Linux and 288 more. ## How do I fix CVE-2017-5753? Apply the vendor's patch. ## Is CVE-2017-5753 being exploited? There is no known exploitation of CVE-2017-5753 in the wild and no public exploit code. Public exploit code: - Example of using revealed "Spectre" exploit (CVE-2017-5753 and CVE-2017-5715) (github_poc): https://github.com/Eugnis/spectre-attack - 2018年1月2日 (CVE-2017-5753 和 CVE-2017-5715) "幽灵" Spectre 漏洞利用 (github_poc): https://github.com/00052/spectre-attack-example - The demo of the speculative execution attack Spectre (CVE-2017-5753, CVE-2017-5715). (github_poc): https://github.com/ixtal23/spectreScope - Spectre (CVE-2017-5753) (CVE-2017-5715). Not By Me. Collected from Book. (github_poc): https://github.com/EdwardOwusuAdjei/Spectre-PoC - Example of using revealed "Spectre" exploit (CVE-2017-5753 and CVE-2017-5715) (github_poc): https://github.com/pedrolucasoliva/spectre-attack-demo - OSX 10.13.2, CVE-2017-5753, Spectre, PoC, C, ASM for OSX, MAC, Intel Arch, Proof of Concept, Hopper.App Output (github_poc): https://github.com/albertleecn/cve-2017-5753 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-5753 and fix it if it is affected. What it is: CVE-2017-5753 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 4 Jan 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-5753 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-5753/ (Markdown: https://insights.sbomify.com/CVE-2017-5753/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5753 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5753 - OSV: https://osv.dev/vulnerability/CVE-2017-5753 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5753/ Summaries are generated and may contain mistakes; the official description above is the record.