# CVE-2017-15597: Memory corruption in n/a

> A malicious guest administrator can trigger hypervisor memory corruption, causing host crashes and potential privilege escalation or information leaks.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-15597, DEBIAN-CVE-2017-15597, GHSA-53jp-4hq4-cmc7, UBUNTU-CVE-2017-15597

## What is CVE-2017-15597?

CVE-2017-15597 is a critical memory corruption vulnerability in Xen Xen, published on 30 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Xen through 4.9.x. Grant copying code made an implication that any grant pin would be accompanied by a suitable page reference. Other portions of code, however, did not match up with that assumption. When such a grant copy operation is being done on a grant of a dying domain, the assumption turns out wrong. A malicious guest administrator can cause hypervisor memory corruption, most likely resulting in host crash and a Denial of Service. Privilege escalation and information leaks cannot be ruled out.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Xen Xen.

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

Apply the vendor's patch.

## Is CVE-2017-15597 being exploited?

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

## Other vulnerabilities in Xen Xen

- [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0)
- [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15597 is a critical memory corruption vulnerability in Xen Xen, published on 30 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15597 in the wild and no public exploit code.

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

## Sources

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

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