CVE-2026-97620

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-86751 (ENISA EUVD) · GHSA-27vj-fv42-fgqc (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/xe: Flush LSC untyped L1 dataport cache after rcs/ccs batches

emit_render_cache_flush() sets PIPE_CONTROL0_HDC_PIPELINE_FLUSH to flush the L2/HDC data cache before fence signalling, but it never requests a flush of the LSC untyped L1 data cache via the 'Untyped Data-Port Cache Flush Enable' bit in PIPE_CONTROL DWord0[11].

Per the Bspec, in 3D pipeline mode HDC Pipeline Flush is documented to also flush/invalidate the untyped L1 cache, but only depending on how HDC_CHICKEN0[13:11] is programmed. Starting with MTL, this coupling between HDC Pipeline Flush and the untyped L1 cache flush no longer holds in practice, regardless of how HDC_CHICKEN0 is programmed, so relying on it is not safe on newer platforms such as BMG. Mesa's Vulkan driver (anv) has been assuming the kernel flushes both caches between submissions, and hit user-visible corruption in apps such as Llama.cpp because of this gap; it now works around it by flushing both caches again from userspace at the end of every command buffer.

Correctness between submissions on the same queue is userspace's responsibility and belongs in Mesa, not the kernel. However, for security we must ensure stale data can't leak through the untyped L1 dataport cache once memory is reclaimed or evicted, which requires the KMD to flush it before releasing memory for reuse.

Prior to MTL, HDC_CHICKEN0 could be programmed (as already done for DG2 via Wa_22010960976/Wa_14013347512) to reliably keep HDC Pipeline Flush coupled to the untyped L1 cache flush, so those platforms are unaffected. Mesa's own anv driver found that on MTL the HW disconnected the two independently of how HDC_CHICKEN0 is programmed, and could not bring the old behavior back even by writing the register by hand; see Mesa commit 7c2ff46a4fc3 ("anv: don't prevent L1 untyped cache flush in 3D mode"). The kernel can't reliably request the flush from the CS on MTL either, so restrict the new PIPE_CONTROL bit to GRAPHICS_VERx100 >= 2000 (Xe2 and later), where it can be relied on.

Explicitly set PIPE_CONTROL0_UNTYPED_DATAPORT_CACHE_FLUSH together with PIPE_CONTROL0_HDC_PIPELINE_FLUSH in emit_render_cache_flush() on Xe2 and later, so the L1 data cache is known clean before memory is released for reuse, without depending on undocumented platform-specific HDC_CHICKEN0 behavior.

Bspec: 56551 (cherry picked from commit 434514b6fe731e873808297c268fc52cdf4a1ce6)

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-97620(2)

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

Patch Availability(15)

These rows come from Ubuntu and OSV. 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, 6.12.107-1~deb12u1, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 84 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-11-18 05:07 UTCEchelonGraph re-scored
  6. 2026-11-18 05:07 UTCVendor advisory
  7. 2026-11-18 05:07 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  8. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 58 more
  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-28 09:55 UTCOSV refresh
  4. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-25 13:47 UTCEchelonGraph re-scored
  8. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-19 10:42 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  15. 2026-10-19 10:25 UTCNVD update
  16. 2026-10-19 09:55 UTCEchelonGraph re-scored
  17. 2026-10-19 09:55 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  18. 2026-10-19 09:39 UTCMITRE cvelistV5
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 02:56 UTCEchelonGraph re-scored
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-10-12 14:39 UTCEchelonGraph re-scored
  28. 2026-10-11 21:32 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  29. 2026-10-11 19:10 UTCEchelonGraph re-scored
  30. 2026-10-11 16:26 UTCEchelonGraph re-scored
  31. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-10-11 13:38 UTCEchelonGraph re-scored
  33. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-10-09 02:12 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  36. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-10-06 06:56 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  40. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-10-03 11:26 UTCNVD update
  44. 2026-10-03 11:20 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  45. 2026-10-03 11:10 UTCMITRE cvelistV5
  46. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-10-01 02:07 UTCEchelonGraph re-scored
  49. 2026-10-01 02:07 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  50. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  51. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-09-28 06:52 UTCEchelonGraph re-scored
  53. 2026-09-28 06:52 UTCGHSA enrichmentGHSA-27vj-fv42-fgqc
  54. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-25 11:30 UTCNVD update
  57. 2026-09-25 10:37 UTCEchelonGraph re-scored
  58. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-97620?
CVE-2026-97620 is a vulnerability whose severity is not yet rated; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe: Flush LSC untyped L1 dataport cache after rcs/ccs batches emit_render_cache_flush() sets PIPE_CONTROL0_HDC_PIPELINE_FLUSH to flush the L2/HDC data cache before fence signalling, but it never requests a flush of the LSC…
When was the CVE record for CVE-2026-97620 published?
The CVE record for CVE-2026-97620 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-97620 actively exploited?
CVE-2026-97620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-97620?
A fix for CVE-2026-97620 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97620 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-97620

Explore →

Is Your Infrastructure Affected by CVE-2026-97620?

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