# CVE-2026-99006: drm/i915/gem: Prevent overstepping exec array boundary


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** AZL-110846, BELL-CVE-2026-99006, DEBIAN-CVE-2026-99006, GHSA-rj8m-rj3g-fqjh, UBUNTU-CVE-2026-99006

## What is CVE-2026-99006?

CVE-2026-99006 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/i915/gem: Prevent overstepping exec array boundary

It is possible for eb_relocate_parse_slow() to call kvfree() on
entries outside the original exec array during following
scenario inside eb_relocate_parse_slow():

1) eb_copy_relocations() allocates as many as eb->buffer_count
   copies for exec entries;
2) eb_parse() appends up to two VMAs, right after incrementing
   eb->buffer_count;
3) cleanup under "out" label uses this incremented buffer_count
   to release relocation pointers from exec array via kvfree(),
   not from VMA array.

To amend this problem, ensure that relocation cleanup uses the
original exec object count, excluding the VMAs appended by the
command parser.

(cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)

## Which versions are affected by CVE-2026-99006?


## How do I fix CVE-2026-99006?

Upgrade to a fixed version.

## Is CVE-2026-99006 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99006 and fix it if it is affected.

What it is: CVE-2026-99006 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99006 in the wild and no public exploit code.

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

## Sources

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

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