# CVE-2026-99208: drm/xe/oa: Zero OA buffer at allocation


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** BELL-CVE-2026-99208, DEBIAN-CVE-2026-99208, GHSA-j8g3-c5f3-w4qh, UBUNTU-CVE-2026-99208

## What is CVE-2026-99208?

CVE-2026-99208 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

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

drm/xe/oa: Zero OA buffer at allocation

ttm_bo_type_kernel BOs are not guaranteed to be zeroed on allocation and
may contain data from previously freed pages. Since the OA buffer is
mmap'able by userspace, this can expose stale kernel memory contents.

Streams opened with DRM_XE_OA_PROPERTY_OA_DISABLED allocate the OA
buffer without calling xe_oa_init_oa_buffer(). Zero the buffer at
allocation to prevent information disclosure through mmap.

The existing zeroing in xe_oa_init_oa_buffer() remains necessary for
zero report-id/timestamp detection on enable/re-enable.

(cherry picked from commit 126c4c5388f9311a390b9b254a835b0cf0f55331)

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


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

Upgrade to a fixed version.

## Is CVE-2026-99208 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99208 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99208 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-99208/ (Markdown: https://insights.sbomify.com/CVE-2026-99208/index.md)
```

## Sources

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

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