# CVE-2014-7252: Memory corruption in n/a

> Local attackers can execute arbitrary code or read kernel memory in TI OMAP mobile devices due to improper data validation in the Syslink driver.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 5 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c58j-gphj-cp8j

## What is CVE-2014-7252?

CVE-2014-7252 is a medium-severity memory corruption vulnerability in n/a, published on 5 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in the Syslink driver for Texas Instruments OMAP mobile processor, as used on NTT DOCOMO ARROWS Tab LTE F-01D, ARROWS X LTE F-05D, Disney Mobile on docomo F-08D, REGZA Phone T-01D, and PRADA phone by LG L-02D; and SoftBank SHARP handsets 102SH allow local users to execute arbitrary code or read kernel memory via unknown vectors related to userland data and "improper data validation."

## Which versions are affected by CVE-2014-7252?

It affects 6 products.


Products: Disney Interactive Disney Mobile, Fujitsu Arrows Tab Lte F-01d, Fujitsu Arrows X Lte F-05d, Fujitsu Regza Phone T-01d, Lg Prada Phone L-02d, Sharp Softbank 102sh.

## How do I fix CVE-2014-7252?

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

## Is CVE-2014-7252 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7252 and fix it if it is affected.

What it is: CVE-2014-7252 is a medium-severity memory corruption vulnerability in n/a, published on 5 Dec 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-7252 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-2014-7252/ (Markdown: https://insights.sbomify.com/CVE-2014-7252/index.md)
```

## Sources

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

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