CVE-2026-68264

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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):

(cherry picked from commit 046045543e530605c441063535e7dca0075369a6)

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
Patch available.
generic

drm/xe/pt: Reset current_op in xe_pt_update_ops_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be5c39730ab8f1dfe59983bf7d8e3705541d1fee
generic

drm/xe/pt: Reset current_op in xe_pt_update_ops_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90e4fd331b980259c40118d05b89b0ec514e7c48
generic

drm/xe/pt: Reset current_op in xe_pt_update_ops_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6384271ac1ac0099198d15df79212a19ebdb929d
generic

drm/xe/pt: Reset current_op in xe_pt_update_ops_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/157b1e3384d7d37f59c0c2b2ff2af8f557db1daa

Vendor Advisories for CVE-2026-68264(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat
redhatkernel-0:5.14.0-687.47.1.el9_82026-09-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 110× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 199 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:51 UTCVendor advisory
  3. 2026-10-04 22:51 UTCGHSA enrichment
  4. 2026-10-04 05:24 UTCEG score recompute
  5. 2026-10-04 05:24 UTCVendor advisory
  6. 2026-10-04 05:24 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 00:54 UTCEG score recompute
  9. 2026-10-03 00:54 UTCVendor advisory
  10. 2026-10-03 00:54 UTCGHSA enrichment
  11. 2026-10-02 17:56 UTCEPSS rescore
  12. 2026-10-02 09:21 UTCEG score recompute
  13. 2026-10-02 09:21 UTCVendor advisory
  14. 2026-10-02 09:21 UTCGHSA enrichment
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-10-01 12:09 UTCVendor advisory
  17. 2026-10-01 12:09 UTCGHSA enrichment
  18. 2026-09-30 22:39 UTCEG score recompute
  19. 2026-09-30 22:39 UTCVendor advisory
  20. 2026-09-30 22:39 UTCGHSA enrichment
  21. 2026-09-30 15:03 UTCEPSS rescore
  22. 2026-09-29 05:24 UTCEG score recompute
  23. 2026-09-29 05:24 UTCVendor advisory
  24. 2026-09-29 05:24 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-28 02:25 UTCEG score recompute
  2. 2026-09-28 02:25 UTCVendor advisory
  3. 2026-09-28 02:25 UTCGHSA enrichment
  4. 2026-09-27 13:48 UTCEPSS rescore
  5. 2026-09-27 13:15 UTCEG score recompute
  6. 2026-09-27 13:15 UTCVendor advisory
  7. 2026-09-27 13:15 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 04:04 UTCEG score recompute
  10. 2026-09-25 04:04 UTCVendor advisory
  11. 2026-09-25 04:04 UTCGHSA enrichment
  12. 2026-09-24 04:09 UTCEG score recompute
  13. 2026-09-24 04:09 UTCVendor advisory
  14. 2026-09-24 04:09 UTCGHSA enrichment
  15. 2026-09-23 17:54 UTCEPSS rescore
  16. 2026-09-23 14:51 UTCVendor advisory
  17. 2026-09-23 14:51 UTCGHSA enrichment
  18. 2026-09-23 01:47 UTCEG score recompute
  19. 2026-09-23 01:47 UTCVendor advisory
  20. 2026-09-23 01:47 UTCGHSA enrichment
  21. 2026-09-22 12:42 UTCVendor advisory
  22. 2026-09-22 12:42 UTCGHSA enrichment
  23. 2026-09-21 23:03 UTCEG score recompute
  24. 2026-09-21 23:03 UTCVendor advisory
  25. 2026-09-21 23:02 UTCGHSA enrichment
  26. 2026-09-21 02:02 UTCEG score recompute
  27. 2026-09-21 02:02 UTCVendor advisory
  28. 2026-09-21 02:02 UTCGHSA enrichment
  29. 2026-09-20 20:16 UTCEPSS rescore
  30. 2026-09-20 10:49 UTCVendor advisory
  31. 2026-09-20 10:49 UTCGHSA enrichment
  32. 2026-09-19 20:03 UTCEG score recompute
  33. 2026-09-19 20:03 UTCVendor advisory
  34. 2026-09-19 20:03 UTCGHSA enrichment
  35. 2026-09-19 06:23 UTCVendor advisory
  36. 2026-09-19 06:23 UTCGHSA enrichment
  37. 2026-09-18 17:18 UTCVendor advisory
  38. 2026-09-18 17:18 UTCGHSA enrichment
  39. 2026-09-18 04:05 UTCEG score recompute
  40. 2026-09-18 04:05 UTCVendor advisory
  41. 2026-09-18 04:05 UTCGHSA enrichment
  42. 2026-09-17 15:01 UTCVendor advisory
  43. 2026-09-17 15:00 UTCGHSA enrichment
  44. 2026-09-17 00:47 UTCEG score recompute
  45. 2026-09-17 00:47 UTCVendor advisory
  46. 2026-09-17 00:47 UTCGHSA enrichment
  47. 2026-09-16 14:08 UTCEPSS rescore
  48. 2026-09-16 05:15 UTCEPSS rescore
  49. 2026-09-16 03:01 UTCVendor advisory
  50. 2026-09-16 03:01 UTCGHSA enrichment
  51. 2026-09-15 13:57 UTCEG score recompute
  52. 2026-09-15 13:57 UTCVendor advisory
  53. 2026-09-15 13:57 UTCGHSA enrichment
  54. 2026-09-15 00:38 UTCGHSA enrichment
  55. 2026-09-14 07:33 UTCGHSA enrichment
  56. 2026-09-13 18:29 UTCEG score recompute
  57. 2026-09-13 18:29 UTCGHSA enrichment
  58. 2026-09-13 05:25 UTCGHSA enrichment
  59. 2026-09-12 16:21 UTCEG score recompute
  60. 2026-09-12 16:21 UTCGHSA enrichment
  61. 2026-09-12 03:17 UTCEG score recompute
  62. 2026-09-12 03:17 UTCGHSA enrichment
  63. 2026-09-11 14:53 UTCEPSS rescore
  64. 2026-09-11 14:13 UTCEG score recompute
  65. 2026-09-11 14:13 UTCGHSA enrichment
  66. 2026-09-11 09:37 UTCEPSS rescore
  67. 2026-09-10 21:08 UTCEG score recompute
  68. 2026-09-10 21:08 UTCGHSA enrichment
  69. 2026-09-10 08:01 UTCGHSA enrichment
  70. 2026-09-09 18:57 UTCEG score recompute
  71. 2026-09-09 18:57 UTCGHSA enrichment
  72. 2026-09-09 05:53 UTCEG score recompute
  73. 2026-09-09 05:53 UTCGHSA enrichment
  74. 2026-09-08 22:01 UTCEPSS rescore
  75. 2026-09-08 07:24 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68264?
CVE-2026-68264 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/pt: Reset currentop in xeptupdateops_init() xeptupdateopsinit() fails to reset current_op to 0. On the vmbind path, opsexecute() calls xeptupdateopsprepare() inside the xevalidationguard() / drmexecuntilalllocked() loop.…
When was CVE-2026-68264 disclosed?
CVE-2026-68264 was first published on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68264 actively exploited?
CVE-2026-68264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68264?
CVE-2026-68264 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68264?
A fix for CVE-2026-68264 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68264 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68264

Explore →

Is Your Infrastructure Affected by CVE-2026-68264?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs