# CVE-2026-74699: drm/xe: Fix memory leak in exec_queue_set_hang_replay_state()

> A memory leak in the Linux kernel's Xe GPU driver allows local attackers to exhaust system memory, potentially causing 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:** 22 Aug 2026
- **Updated:** 22 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-74699, GHSA-phjm-6f6w-c4wh, UBUNTU-CVE-2026-74699

## What is CVE-2026-74699?

CVE-2026-74699 is a memory corruption vulnerability in Linux, published on 22 Aug 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/xe: Fix memory leak in exec_queue_set_hang_replay_state()

The q->replay_state is blindly overwritten, which can potentially leak
memory that was previously allocated by vmemdup_user().
Return an error if q->replay_state is not empty.

Discovered using AI-assisted static analysis confirmed by Intel Product
Security.

(cherry picked from commit f6b6cc1118bdbc4265fa8b3bdf8565b26f13e56e)

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


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

Apply the vendor's patch.

## Is CVE-2026-74699 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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