What is CVE-2026-68264?

CVE-2026-68264 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.12 onward and patched in 6.12.103, 6.18.44, 7.1.6 and others. CVE-2026-68264 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-68264?

CVE-2026-68264 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-68264?

Yes, CVE-2026-68264 has been patched. Fixed versions include 6.12.103, 6.18.44, 7.1.6 and others. If you are running Linux kernel 6.12 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-68264 actively exploited?

CVE-2026-68264 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-68264

High

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)

Package Linux Kernel

Published 2026-08-10

Last modified 2026-08-17

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.12 and later are affected. Fixed in 6.12.103, 6.18.44, 7.1.6, 7.2 and their respective stable series.

Affected from

≥ 6.12

Fixed in

✓ 6.12.103 6.12.x ✓ 6.18.44 6.18.x ✓ 7.1.6 7.1.x ✓ 7.2

References

4 total

Details

CVE ID CVE-2026-68264

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-08-10

Modified 2026-08-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-68264?

CVE-2026-68264 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.12 onward and has been patched in 6.12.103, 6.18.44, 7.1.6 and others. CVE-2026-68264 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-68264?

CVE-2026-68264 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-68264?

Yes. CVE-2026-68264 has been patched. Fixed versions include 6.12.103, 6.18.44, 7.1.6 and others. If you are running Linux kernel 6.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-68264 actively exploited?

No. CVE-2026-68264 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.