# CVE-2017-5925: Page table walks conducted by the MMU during virtual to physical address translation leave a trace in the last level cache of modern Intel processors.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pm4h-mm7m-wp4j

## What is CVE-2017-5925?

CVE-2017-5925 is a high-severity vulnerability in n/a, published on 27 Feb 2017. 

### Official description

Page table walks conducted by the MMU during virtual to physical address translation leave a trace in the last level cache of modern Intel processors. By performing a side-channel attack on the MMU operations, it is possible to leak data and code pointers from JavaScript, breaking ASLR.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-5925?

It affects 20 products.


Products: Allwinner A64, Amd Athlon Ii 640 X4, Amd E-350, Amd Fx-8120 8-Core, Amd Fx-8320 8-Core, Amd Fx-8350 8-Core, Amd Phenom 9550 4-Core, Intel Atom C2750, Intel Celeron N2840, Intel Core I5 M480, Intel Core I7-2620qm, Intel Core I7-3632qm, Intel Core I7-4500u, Intel Core I7-6700k, Intel Core I7 920, Intel Xeon E3-1240 V5, Intel Xeon E5-2658 V2, Nvidia Tegra K1 Cd570m-A1, Nvidia Tegra K1 Cd580m-A1, Samsung Exynos 5800.

## How do I fix CVE-2017-5925?

No fix has been published for CVE-2017-5925 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5925 being exploited?

There is no known exploitation of CVE-2017-5925 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-5926](https://insights.sbomify.com/CVE-2017-5926/): Page table walks conducted by the MMU during virtual to physical address translation leave a trace in the last level cache of modern AMD processors. (high 7.5)
- [CVE-2017-5927](https://insights.sbomify.com/CVE-2017-5927/): Page table walks conducted by the MMU during virtual to physical address translation leave a trace in the last level cache of modern ARM processors. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5925 and fix it if it is affected.

What it is: CVE-2017-5925 is a high-severity vulnerability in n/a, published on 27 Feb 2017. 
Exploitation: There is no known exploitation of CVE-2017-5925 in the wild and no public exploit code.

Affected product: n/a. 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-5925/ (Markdown: https://insights.sbomify.com/CVE-2017-5925/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5925
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5925
- OSV: https://osv.dev/vulnerability/CVE-2017-5925

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5925/
Summaries are generated and may contain mistakes; the official description above is the record.