# CVE-2026-68265: drm/xe/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC

> A null dereference in the Linux kernel's DRM Xe driver allows local attackers to cause a denial of service via improper memory advice handling.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`)
- **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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68265, DEBIAN-CVE-2026-68265, GHSA-298g-42h7-52m6, UBUNTU-CVE-2026-68265

## What is CVE-2026-68265?

CVE-2026-68265 is a high-severity 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/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC

When prefetch region is DRM_XE_CONSULT_MEM_ADVISE_PREF_LOC for a BO VMA,
the code used it as an index into region_to_mem_type[], causing an
out-of-bounds access since the value is -1.

Resolve the preferred location for BO VMAs directly: local VRAM on dGFX
(using the BO's tile placement) or system memory on iGPU.

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

v2:
-Fix null dereference

(cherry picked from commit d9a4906ac03be9f6ed3f3b45c56c866b867fd75b)

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-68265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68265 is a high-severity 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-68265 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-68265/ (Markdown: https://insights.sbomify.com/CVE-2026-68265/index.md)
```

## Sources

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

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