Answer in brief
CVE-2026-68264 records a Unknown severity vulnerability in drm/xe/pt: Reset current_op in xe_pt_update_ops_init(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <be5c39730ab8f1dfe59983bf7d8e3705541d1fee || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <157b1e3384d7d37f59c0c2b2ff2af8f557db1daa || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <90e4fd331b980259c40118d05b89b0ec514e7c48 || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <6384271ac1ac0099198d15df79212a19ebdb929d | be5c39730ab8f1dfe59983bf7d8e3705541d1fee, 157b1e3384d7d37f59c0c2b2ff2af8f557db1daa, 90e4fd331b980259c40118d05b89b0ec514e7c48, 6384271ac1ac0099198d15df79212a19ebdb929d |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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 [email protected] (cherry picked from commit 046045543e530605c441063535e7dca0075369a6)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68264 records a Unknown severity vulnerability in drm/xe/pt: Reset current_op in xe_pt_update_ops_init(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <be5c39730ab8f1dfe59983bf7d8e3705541d1fee || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <157b1e3384d7d37f59c0c2b2ff2af8f557db1daa || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <90e4fd331b980259c40118d05b89b0ec514e7c48 || >=e8babb280b5ef904df54b3a90e5a7e3a9600c4a9 <6384271ac1ac0099198d15df79212a19ebdb929d | be5c39730ab8f1dfe59983bf7d8e3705541d1fee, 157b1e3384d7d37f59c0c2b2ff2af8f557db1daa, 90e4fd331b980259c40118d05b89b0ec514e7c48, 6384271ac1ac0099198d15df79212a19ebdb929d |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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 [email protected] (cherry picked from commit 046045543e530605c441063535e7dca0075369a6)
Quoted source text, attributed separately from HOL analysis.