CVE-2026-68274

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/guc: Fix buffer overflow in steered register list allocation

The size calculation for the steered register extarray uses only the geometry DSS mask (g_dss_mask) to determine the number of entries to allocate:

total = bitmap_weight(gt->fuse_topo.g_dss_mask, ...) * steer_reg_num;

However, the filling loop uses for_each_dss_steering(), which iterates over for_each_dss(), defined as the union of g_dss_mask and c_dss_mask (geometry + compute DSS). On platforms with compute-only DSS bits, the loop writes past the allocated buffer, corrupting adjacent slab objects.

This manifests as list_del corruption and SLUB redzone overwrites during drm_managed_release on device unbind, since the overflow corrupts the drmres list_head of neighboring allocations.

Fix by computing the allocation size using the union of both DSS masks, matching the iteration pattern of for_each_dss_steering().

-- v2:

  • use bitmap_weighted_or() (Zhanjun)

(cherry picked from commit 0a78a44f4901aa6c9263e66be7fce02282f1109f)

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
5%
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/guc: Fix buffer overflow in steered register list allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/xe/guc: Fix buffer overflow in steered register list allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/xe/guc: Fix buffer overflow in steered register list allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/632ecc90e1ca5d3b6822bb4d08f84a175b6c42c0

Vendor Advisories for CVE-2026-68274(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 31× in last 7d / 43× 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 01:39 UTCEG score recompute
  2. 2026-08-21 01:39 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:39 UTCGHSA enrichment
  5. 2026-08-19 23:41 UTCEG score recompute
  6. 2026-08-19 23:41 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:42 UTCGHSA enrichment
  9. 2026-08-18 21:40 UTCEG score recompute
  10. 2026-08-18 21:40 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:22 UTCGHSA enrichment
  14. 2026-08-17 19:20 UTCEG score recompute
  15. 2026-08-17 19:20 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:37 UTCEG score recompute
  18. 2026-08-17 05:37 UTCGHSA enrichment
  19. 2026-08-17 05:07 UTCEG score recompute
  20. 2026-08-17 05:07 UTCGHSA enrichment
  21. 2026-08-16 16:40 UTCEG score recompute
  22. 2026-08-16 16:40 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 03:39 UTCEG score recompute
  25. 2026-08-16 03:39 UTCGHSA enrichment
Show 18 more
  1. 2026-08-15 14:41 UTCGHSA enrichment
  2. 2026-08-15 01:42 UTCEG score recompute
  3. 2026-08-15 01:42 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 12:44 UTCEG score recompute
  6. 2026-08-14 12:44 UTCGHSA enrichment
  7. 2026-08-13 23:46 UTCEG score recompute
  8. 2026-08-13 23:46 UTCGHSA enrichment
  9. 2026-08-13 22:44 UTCEG score recompute 7.80
  10. 2026-08-13 22:44 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 09:12 UTCEG score recompute
  14. 2026-08-13 09:12 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-10 13:24 UTCNVD update
  17. 2026-08-10 12:19 UTCEG score recompute
  18. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68274?
CVE-2026-68274 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Fix buffer overflow in steered register list allocation The size calculation for the steered register extarray uses only the geometry DSS mask (gdssmask) to determine the number of entries to allocate: total =…
When was CVE-2026-68274 disclosed?
CVE-2026-68274 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-68274 actively exploited?
CVE-2026-68274 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 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68274?
CVE-2026-68274 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68274, 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-68274

Explore →

Is Your Infrastructure Affected by CVE-2026-68274?

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