# CVE-2015-7891: Race condition in n/a

> Local attackers can exploit a race condition in the Samsung Graphics 2D driver to trigger memory errors, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 2 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-59gr-vjcr-m2p7

## What is CVE-2015-7891?

CVE-2015-7891 is a high-severity vulnerability in n/a, published on 2 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in the ioctl implementation in the Samsung Graphics 2D driver (aka /dev/fimg2d) in Samsung devices with Android L(5.0/5.1) allows local users to trigger memory errors by leveraging definition of g2d_lock and g2d_unlock lock macros as no-ops, aka SVE-2015-4598.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Samsung Samsung Mobile.

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

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

## Is CVE-2015-7891 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7891 exists.

Public exploit code:

- Samsung fimg2d - FIMG2D_BITBLT_BLIT ioctl Concurrency Flaw (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-9139](https://insights.sbomify.com/CVE-2018-9139/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-9143](https://insights.sbomify.com/CVE-2018-9143/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-5538](https://insights.sbomify.com/CVE-2017-5538/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9965](https://insights.sbomify.com/CVE-2016-9965/): Denial of service in n/a (critical 9.8)
- [CVE-2016-9966](https://insights.sbomify.com/CVE-2016-9966/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7891 is a high-severity vulnerability in n/a, published on 2 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7891 exists.

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-7891/ (Markdown: https://insights.sbomify.com/CVE-2015-7891/index.md)
```

## Sources

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

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