# CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists

> A local attacker can bypass security restrictions to access restricted OA registers in the Linux kernel's Xe GPU driver due to missing privilege denial bits.

- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68267, DEBIAN-CVE-2026-68267, GHSA-98pm-wggw-r936, UBUNTU-CVE-2026-68267

## What is CVE-2026-68267?

CVE-2026-68267 is a vulnerability in Linux, published on 10 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/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists

Unconditionally whitelisting OA registers is a security violation. Set
RING_FORCE_TO_NONPRIV_DENY bit in OA nonpriv slots, so that OA registers
don't get whitelisted by default after probe, gt reset, resume and engine
reset.

(cherry picked from commit 90511bdcfda97211c01f1d945d4ea616578d8fca)

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


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

Apply the vendor's patch.

## Is CVE-2026-68267 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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