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

> Attackers can exploit memory corruption in the Samsung S4 kernel driver to cause denial of service or gain elevated privileges.

- **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:** No
- **Published:** 24 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hrv8-h75j-8fcw

## What is CVE-2015-1801?

CVE-2015-1801 is a critical memory corruption vulnerability in n/a, published on 24 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The samsung_extdisp driver in the Samsung S4 (GT-I9500) I9500XXUEMK8 kernel 3.4 and earlier allows attackers to cause a denial of service (memory corruption) or gain privileges.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Samsung Galaxy S4 Firmware.

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

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

## Is CVE-2015-1801 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-1800](https://insights.sbomify.com/CVE-2015-1800/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1801 is a critical memory corruption vulnerability in n/a, published on 24 Aug 2017. 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-1801 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-2015-1801/ (Markdown: https://insights.sbomify.com/CVE-2015-1801/index.md)
```

## Sources

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

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