# CVE-2018-12222: Memory corruption in Intel(R) Graphics Driver for Windows

> An unprivileged local attacker can trigger an out-of-bounds memory read in the Intel Graphics Driver kernel mode driver due to insufficient input validation.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 14 Mar 2019
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-2c4w-vq26-43mv

## What is CVE-2018-12222?

CVE-2018-12222 is a low-severity memory corruption vulnerability in Intel Graphics Driver, published on 14 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient input validation in Kernel Mode Driver in Intel(R) Graphics Driver for Windows* before versions 10.18.x.5059 (aka 15.33.x.5059), 10.18.x.5057 (aka 15.36.x.5057), 20.19.x.5063 (aka 15.40.x.5063) 21.20.x.5064 (aka 15.45.x.5064) and 24.20.100.6373 potentially enables an unprivileged user to cause an out of bound memory read via local access.

Weakness: CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2018-12222?

It affects 1 product.


Products: Intel Graphics Driver.

## How do I fix CVE-2018-12222?

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

## Is CVE-2018-12222 being exploited?

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

## Other vulnerabilities in Intel Graphics Driver

- [CVE-2018-12214](https://insights.sbomify.com/CVE-2018-12214/): Memory corruption in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2018-12216](https://insights.sbomify.com/CVE-2018-12216/): Code injection in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2018-12220](https://insights.sbomify.com/CVE-2018-12220/): Privilege escalation in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2020-0504](https://insights.sbomify.com/CVE-2020-0504/): Memory corruption in Intel(R) Graphics Drivers (high 7.8)
- [CVE-2020-0508](https://insights.sbomify.com/CVE-2020-0508/): Privilege escalation in Intel(R) Graphics Drivers (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12222 and fix it if it is affected.

What it is: CVE-2018-12222 is a low-severity memory corruption vulnerability in Intel Graphics Driver, published on 14 Mar 2019. 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-2018-12222 in the wild and no public exploit code.

Affected product: Intel Graphics Driver. 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-2018-12222/ (Markdown: https://insights.sbomify.com/CVE-2018-12222/index.md)
```

## Sources

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

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