# CVE-2026-80903: drm/xe/oa: Fix sync entry leak on OA config emit failure

> A memory leak in the Linux kernel's Xe GPU driver allows local attackers to exhaust kernel memory, 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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80903, DEBIAN-CVE-2026-80903, GHSA-xqfj-m7qf-gr42, UBUNTU-CVE-2026-80903

## What is CVE-2026-80903?

CVE-2026-80903 is a memory corruption vulnerability in Linux, published on 4 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/xe/oa: Fix sync entry leak on OA config emit failure

xe_oa_emit_oa_config() releases the sync entries and the syncs array
only on its success path. When it fails before the point of no return
(fence allocation, config buffer allocation or batch submission), it
returns without touching stream->syncs.

The stream open path handles such failures in the caller, but
xe_oa_config_locked() propagates the error without any cleanup, so the
syncs array and the fence references held by the parsed entries are
leaked. The next config ioctl overwrites stream->syncs, making the
memory unreachable for good.

Clean up the parsed syncs when xe_oa_emit_oa_config() fails, matching
the cleanup done by the stream open error path.

(cherry picked from commit 8af97b3da2cfce04e6b457c6eb17ed3c1daf912b)

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


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

Apply the vendor's patch.

## Is CVE-2026-80903 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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