# CVE-2016-9038: Race condition in X

> A local attacker can exploit a race condition in the Invincea X driver to corrupt kernel memory and escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/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:** 24 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-ff7m-858p-5r2m

## What is CVE-2016-9038?

CVE-2016-9038 is a high-severity vulnerability in Invincea X, published on 24 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable double fetch vulnerability exists in the SboxDrv.sys driver functionality of Invincea-X 6.1.3-24058. A specially crafted input buffer and race condition can result in kernel memory corruption, which could result in privilege escalation. An attacker needs to execute a special application locally to trigger this vulnerability.

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

## Which versions are affected by CVE-2016-9038?

It affects 1 product.


Products: Sophos Invincea-X.

## How do I fix CVE-2016-9038?

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

## Is CVE-2016-9038 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9038 and fix it if it is affected.

What it is: CVE-2016-9038 is a high-severity vulnerability in Invincea X, published on 24 Apr 2018. 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-2016-9038 in the wild and no public exploit code.

Affected product: Invincea X. 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-2016-9038/ (Markdown: https://insights.sbomify.com/CVE-2016-9038/index.md)
```

## Sources

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

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