# CVE-2019-11085: Privilege escalation in Intel(R) i915 Graphics for Linux

> An authenticated local user can escalate privileges due to insufficient input validation in the Intel i915 Linux kernel driver.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/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:** Yes
- **Published:** 17 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11085, GHSA-2wcq-j266-p9cq, UBUNTU-CVE-2019-11085

## What is CVE-2019-11085?

CVE-2019-11085 is a high-severity vulnerability in Intel(R) i915 Graphics for Linux, published on 17 May 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) i915 Graphics for Linux before version 5.0 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-11085?

It affects 1 product.


Products: Intel I915 Firmware.

## How do I fix CVE-2019-11085?

Upgrade to a fixed version.

## Is CVE-2019-11085 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11085 and fix it if it is affected.

What it is: CVE-2019-11085 is a high-severity vulnerability in Intel(R) i915 Graphics for Linux, published on 17 May 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-2019-11085 in the wild and no public exploit code.

Affected product: Intel(R) i915 Graphics for Linux. 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-2019-11085/ (Markdown: https://insights.sbomify.com/CVE-2019-11085/index.md)
```

## Sources

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

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