CVE-2026-68298

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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 — 3 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%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create()

Commit 9e9787414882 ("drm/xe/userptr: replace xe_hmm with gpusvm") made xe_svm_init() unconditional in xe_vm_create() and extended it to also initialize a "simple" gpusvm state for non-fault-mode VMs. The matching xe_svm_fini() call in xe_vm_close_and_put() was updated to run unconditionally, but the error unwind path in xe_vm_create() was not.

On the drm_gpuvm_resv_object_alloc() failure path, xe_svm_init() has already succeeded but xe_svm_fini() is only called when XE_VM_FLAG_FAULT_MODE is set. For non-fault-mode VMs this leaves vm->svm.gpusvm partially initialized and leaks the resources allocated by drm_gpusvm_init().

For fault-mode VMs, xe_svm_init() additionally acquires the pagemap owner via drm_pagemap_acquire_owner() and the pagemaps via xe_svm_get_pagemaps(). Those resources are released by xe_svm_close(), not xe_svm_fini(). On the same error path, xe_svm_close() is not called either, so fault-mode VMs leak the pagemap owner and pagemaps.

Fix both leaks:

  • Call xe_svm_fini() unconditionally on the err_svm_fini path, matching
the unconditional xe_svm_init() call. Move the vm->size = 0 assignment out of the conditional so the xe_vm_is_closed() assert in xe_svm_fini() (and xe_svm_close()) holds for both modes.
  • Call xe_svm_close() for fault-mode VMs before xe_svm_fini(), matching
the ordering used in xe_vm_close_and_put().

(cherry picked from commit ca2a3587d577ba764e0fe628fb676244fc33ddd4)

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ac92736030f3395d970c300eaeb59ac258a0c3e
generic

drm/xe/vm: Fix SVM leak on resv obj alloc failure in xe_vm_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/279339aa8bdcf9db40094cf2bcbd495c53dbe817

Vendor Advisories for CVE-2026-68298(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 44× 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.

  1. 2026-08-21 03:19 UTCEG score recompute
  2. 2026-08-21 03:19 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:46 UTCGHSA enrichment
  5. 2026-08-20 04:14 UTCEG score recompute
  6. 2026-08-20 04:14 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:42 UTCGHSA enrichment
  9. 2026-08-19 05:07 UTCGHSA enrichment
  10. 2026-08-18 17:25 UTCEG score recompute
  11. 2026-08-18 17:25 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 04:41 UTCGHSA enrichment
  15. 2026-08-17 17:09 UTCEG score recompute
  16. 2026-08-17 17:09 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 05:37 UTCEG score recompute
  19. 2026-08-17 05:37 UTCGHSA enrichment
  20. 2026-08-17 05:06 UTCEG score recompute
  21. 2026-08-17 05:06 UTCGHSA enrichment
  22. 2026-08-16 20:56 UTCEG score recompute
  23. 2026-08-16 20:56 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 09:24 UTCEG score recompute
Show 19 more
  1. 2026-08-16 09:24 UTCGHSA enrichment
  2. 2026-08-15 21:53 UTCGHSA enrichment
  3. 2026-08-15 10:21 UTCEG score recompute
  4. 2026-08-15 10:21 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 22:49 UTCGHSA enrichment
  7. 2026-08-14 11:18 UTCEG score recompute
  8. 2026-08-14 11:18 UTCGHSA enrichment
  9. 2026-08-13 23:46 UTCEG score recompute
  10. 2026-08-13 23:46 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCEG score recompute▲ 7.80
  12. 2026-08-13 22:44 UTCGHSA enrichment
  13. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-13 13:29 UTCEG score recompute
  15. 2026-08-13 13:29 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:19 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68298?
CVE-2026-68298 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/vm: Fix SVM leak on resv obj alloc failure in xevmcreate() Commit 9e9787414882 ("drm/xe/userptr: replace xe_hmm with gpusvm") made xesvminit() unconditional in xevmcreate() and extended it to also initialize a "simple"…
When was CVE-2026-68298 disclosed?
CVE-2026-68298 was first published in the National Vulnerability Database 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-68298 actively exploited?
CVE-2026-68298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68298?
CVE-2026-68298 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68298?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68298, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68298

Explore →

Is Your Infrastructure Affected by CVE-2026-68298?

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

Start Free Scan →Browse All CVEs