# CVE-2015-6792: Memory corruption in n/a

> Remote attackers can execute arbitrary code or crash the browser via improper data handling in the MIDI subsystem.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gr4r-9v54-jxjh, MGASA-2015-0479, UBUNTU-CVE-2015-6792

## What is CVE-2015-6792?

CVE-2015-6792 is a critical memory corruption vulnerability in Google Chrome, published on 24 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MIDI subsystem in Google Chrome before 47.0.2526.106 does not properly handle the sending of data, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors, related to midi_manager.cc, midi_manager_alsa.cc, and midi_manager_mac.cc, a different vulnerability than CVE-2015-8664.

## Which versions are affected by CVE-2015-6792?

It affects 1 product.


Products: Google Chrome.

## How do I fix CVE-2015-6792?

Upgrade to a fixed version.

## Is CVE-2015-6792 being exploited?

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

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6792 and fix it if it is affected.

What it is: CVE-2015-6792 is a critical memory corruption vulnerability in Google Chrome, published on 24 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6792 in the wild and no public exploit code.

Affected product: Google Chrome. 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-2015-6792/ (Markdown: https://insights.sbomify.com/CVE-2015-6792/index.md)
```

## Sources

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

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