EudorIACyber Intelligence
Operational monitoring Newsletter IT EN
← Back to intelligence
Vulnerability

CVE-2026-97620: 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 da

Official source
EudorIA operational summary

What it means

Priority 45/100

NIST National Vulnerability Database ha pubblicato CVE-2026-97620. La rilevanza va confermata rispetto alle tecnologie effettivamente in uso.

Why it matters

Il segnale diventa operativo solo se prodotto, versione o servizio sono presenti nel perimetro.

AudienceITSOCCISO
Information centre

Translation in progress

NIST National Vulnerability Database

The official content is available in the original language. The Italian version will be published once automated checks are complete.

Text acquired from the source

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 regi

Source
NIST National Vulnerability Database
Publishing entity
NIST National Vulnerability Database
Entity type
National authority
Area
North America · US
Original language
en · translation in preparation
Publication
25/09/2026 13:17
CVE
CVE-2026-97620
Stated country
US
Technical scope

Affected products and versions

Not published
No structured range published.

The official sources queried do not yet expose a list of affected versions. No automatic inference is made.

Sources for the versionsNIST National Vulnerability Database
Open the original source