# CVE-2013-4740: Race condition in n/a

> A race condition in the Goodix touchscreen driver allows local attackers to cause memory corruption, leading to privilege escalation or denial of service.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 12 Nov 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gppg-f967-2v7c

## What is CVE-2013-4740?

CVE-2013-4740 is a medium-severity vulnerability in n/a, published on 12 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

goodix_tool.c in the Goodix gt915 touchscreen driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, relies on user-space length values for kernel-memory copies of procfs file content, which allows attackers to gain privileges or cause a denial of service (memory corruption) via an application that provides crafted values.

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

## Which versions are affected by CVE-2013-4740?

It affects 1 product.


Products: Qualcomm Quic Mobile Station Modem Kernel.

## How do I fix CVE-2013-4740?

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

## Is CVE-2013-4740 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4737](https://insights.sbomify.com/CVE-2013-4737/): Security feature bypass in n/a (critical 9.3)
- [CVE-2013-6122](https://insights.sbomify.com/CVE-2013-6122/): Race condition in n/a (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4740 and fix it if it is affected.

What it is: CVE-2013-4740 is a medium-severity vulnerability in n/a, published on 12 Nov 2013. 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-2013-4740 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-2013-4740/ (Markdown: https://insights.sbomify.com/CVE-2013-4740/index.md)
```

## Sources

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

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