# CVE-2026-97899: drm/i915: Fix memory leak in query_perf_config_list()

> A memory leak in the i915 graphics driver allows local attackers to exhaust kernel memory, potentially causing a denial of service.

- **Severity:** Not scored
- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104222, BELL-CVE-2026-97899, DEBIAN-CVE-2026-97899, GHSA-jqpp-x7c4-x6fg, UBUNTU-CVE-2026-97899

## What is CVE-2026-97899?

CVE-2026-97899 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

drm/i915: Fix memory leak in query_perf_config_list()

When krealloc() fails, free the original oa_config_ids before returning
to avoid a memory leak.

(cherry picked from commit 9977e9d84f46d4f12ad35fbbc0ec4638554bce87)

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


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

Apply the vendor's patch.

## Is CVE-2026-97899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97899 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. 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-2026-97899 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-97899/ (Markdown: https://insights.sbomify.com/CVE-2026-97899/index.md)
```

## Sources

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

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