CVE-2026-90047
drm/xe: Don't hand out the flat CCS storage as usable VRAM
Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't hand out the flat CCS storage as usable VRAM get_flat_ccs_offset() reads the base of the flat CCS storage from the hardware, scales it by the number of enabled L3 nodes, and rounds the result up to 128K. Everything below that offset is then handed to the VRAM allocator as usable memory. Rounding a limit that means "usable memory ends here" upwards publishes whatever lies between the real base and the rounded one as free memory, and that memory belongs to the compression hardware. The scaled value has no reason to be 128K aligned, and on a Battlemage G21 with 16 GiB it is not: flat CCS base: raw 0x3fafff800, rounded 0x3fb000000 so the last 2 KiB of page 0x3fafff000 is CCS storage, in the allocator's pool. Whatever is allocated there gets that tail overwritten by the compression hardware, which needs no page-table entry, no buffer object and no GPU submission to do it, and does it before userspace exists. On this machine a Mesa VM's level-3 page table landed on that page on every cold boot. It lost the entry covering the compositor's batch-buffer heap, so the compositor's first submission faulted fetching its batch and gdm restarted it forever: a black screen on an otherwise working machine. Restarting gdm cleared it because the next VM's page tables were allocated somewhere else. Round down instead, to the page size the allocator works in. On this machine that excludes exactly one page. Reading the reserved page afterwards shows what had been writing it: [369] 0xcccc000000000000 [371] 0xcc77000000000000 [373] 0xcccc000000000000 [375] 0xcc77000000000000 compression metadata, two bytes per sixteen, sitting where the driver used to hand out memory. The assertion that should have caught this compares the offset against GSMBASE - ccs_size for equality. That value is 128K aligned, so it agrees with the rounded-up offset precisely when the base is not aligned - the check cannot fail in the case it exists to catch, and is compiled out unless CONFIG_DRM_XE_DEBUG is set. Replace it with one that can fail: CCS storage must not run into GSM. [ And this was a debug session from hell, enormously helped by an AI doing much of the grunt-work. I'd like to call it my tireless helper, but the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it. I suspect those things have been trained by people who may not be quite as stubborn as I am. But while the AI was ready to give up several times, it did keep adding debug code and analyzing it faithfully when I pushed. So credit where credit is due and I let the AI write the commit message above. This is basically a one-liner fixing a bogus "round_up()" to a "round_down()", but there were 24 patches adding more and more debug information to this, and 18 kernel boot to finally narrow it down to this. - Linus ]
INFO
Published Date :
Sept. 16, 2026, 11:17 a.m.
Last Modified :
Oct. 19, 2026, 9:18 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Round down memory offsets instead of rounding up.
- Update memory allocator configuration.
- Ensure CCS storage does not overlap with GSM.
- Apply the latest kernel patches.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-90047.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-90047 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-90047
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-90047 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-90047 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 19, 2026
Action Type Old Value New Value Added Affected Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/90xxx/CVE-2026-90047.json">CVE-2026-90047</a> -
CVE Translated by [email protected]
Sep. 28, 2026
Action Type Old Value New Value Added Translation Title: la biblioteca CGM_NIST_Loader.dll en JT2Go, Teamcenter Visualization, Description: En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: drm/xe: No entregar el almacenamiento CCS plano como VRAM utilizable get_flat_ccs_offset() lee la base del almacenamiento CCS plano del hardware, lo escala por el número de nodos L3 habilitados y redondea el resultado al alza a 128K. Todo lo que está por debajo de ese desplazamiento se entrega entonces al asignador de VRAM como memoria utilizable. Redondear un límite que significa 'la memoria utilizable termina aquí' hacia arriba publica lo que se encuentra entre la base real y la redondeada como memoria libre, y esa memoria pertenece al hardware de compresión. El valor escalado no tiene razón para estar alineado a 128K, y en un Battlemage G21 con 16 GiB no lo está: base CCS plana: en bruto 0x3fafff800, redondeado 0x3fb000000 así que los últimos 2 KiB de la página 0x3fafff000 son almacenamiento CCS, en el pool del asignador. Lo que sea que se asigne allí ve esa cola sobrescrita por el hardware de compresión, el cual no necesita una entrada en la tabla de páginas, ningún objeto de búfer y ninguna envío a la GPU para hacerlo, y lo hace antes de que exista el espacio de usuario. En esta máquina, la tabla de páginas de nivel 3 de una VM de Mesa aterrizó en esa página en cada arranque en frío. Perdió la entrada que cubría el heap del búfer de lotes del compositor, por lo que el primer envío del compositor falló al recuperar su lote y gdm lo reinició indefinidamente: una pantalla negra en una máquina que, por lo demás, funcionaba. Reiniciar gdm lo solucionó porque las tablas de páginas de la siguiente VM se asignaron en otro lugar. Redondear hacia abajo en su lugar, al tamaño de página en el que trabaja el asignador. En esta máquina, eso excluye exactamente una página. Leer la página reservada después muestra lo que la había estado escribiendo: [369] 0xcccc000000000000 [371] 0xcc77000000000000 [373] 0xcccc000000000000 [375] 0xcc77000000000000 metadatos de compresión, dos bytes por cada dieciséis, ubicados donde el controlador solía entregar memoria. La aserción que debería haber detectado esto compara el desplazamiento con GSMBASE - ccs_size para igualdad. Ese valor está alineado a 128K, por lo que concuerda con el desplazamiento redondeado al alza precisamente cuando la base no está alineada; la verificación no puede fallar en el caso que existe para detectar, y se compila fuera a menos que CONFIG_DRM_XE_DEBUG esté configurado. Reemplácela con una que pueda fallar: El almacenamiento CCS no debe invadir GSM. [ Y esta fue una sesión de depuración infernal, enormemente ayudada por una IA que hizo gran parte del trabajo pesado. Me gustaría llamarlo mi ayudante incansable, pero la IA varias veces afirmó rotundamente que esto era imposible e irresoluble y que simplemente deberíamos escribir un informe al respecto. Sospecho que esas cosas han sido entrenadas por personas que quizás no sean tan tercas como yo. Pero aunque la IA estuvo lista para rendirse varias veces, siguió añadiendo código de depuración y analizándolo fielmente cuando la presioné. Así que, al César lo que es del César, y dejé que la IA escribiera el mensaje de commit anterior. Esto es básicamente una línea que corrige un “round_up()” erróneo a un “round_down()”, pero hubo 24 parches que añadieron cada vez más información de depuración a esto, y 18 arranques del kernel para finalmente reducirlo a esto. - Linus ] -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 16, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 16, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't hand out the flat CCS storage as usable VRAM get_flat_ccs_offset() reads the base of the flat CCS storage from the hardware, scales it by the number of enabled L3 nodes, and rounds the result up to 128K. Everything below that offset is then handed to the VRAM allocator as usable memory. Rounding a limit that means "usable memory ends here" upwards publishes whatever lies between the real base and the rounded one as free memory, and that memory belongs to the compression hardware. The scaled value has no reason to be 128K aligned, and on a Battlemage G21 with 16 GiB it is not: flat CCS base: raw 0x3fafff800, rounded 0x3fb000000 so the last 2 KiB of page 0x3fafff000 is CCS storage, in the allocator's pool. Whatever is allocated there gets that tail overwritten by the compression hardware, which needs no page-table entry, no buffer object and no GPU submission to do it, and does it before userspace exists. On this machine a Mesa VM's level-3 page table landed on that page on every cold boot. It lost the entry covering the compositor's batch-buffer heap, so the compositor's first submission faulted fetching its batch and gdm restarted it forever: a black screen on an otherwise working machine. Restarting gdm cleared it because the next VM's page tables were allocated somewhere else. Round down instead, to the page size the allocator works in. On this machine that excludes exactly one page. Reading the reserved page afterwards shows what had been writing it: [369] 0xcccc000000000000 [371] 0xcc77000000000000 [373] 0xcccc000000000000 [375] 0xcc77000000000000 compression metadata, two bytes per sixteen, sitting where the driver used to hand out memory. The assertion that should have caught this compares the offset against GSMBASE - ccs_size for equality. That value is 128K aligned, so it agrees with the rounded-up offset precisely when the base is not aligned - the check cannot fail in the case it exists to catch, and is compiled out unless CONFIG_DRM_XE_DEBUG is set. Replace it with one that can fail: CCS storage must not run into GSM. [ And this was a debug session from hell, enormously helped by an AI doing much of the grunt-work. I'd like to call it my tireless helper, but the AI several times stated flat out that this was impossible and unsolvable and that we should just write a report about it. I suspect those things have been trained by people who may not be quite as stubborn as I am. But while the AI was ready to give up several times, it did keep adding debug code and analyzing it faithfully when I pushed. So credit where credit is due and I let the AI write the commit message above. This is basically a one-liner fixing a bogus "round_up()" to a "round_down()", but there were 24 patches adding more and more debug information to this, and 18 kernel boot to finally narrow it down to this. - Linus ] Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/90xxx/CVE-2026-90047.json">CVE-2026-90047</a> Added Reference https://git.kernel.org/stable/c/348c3db4f1520d36764ac8cae2492f50599714f6 Added Reference https://git.kernel.org/stable/c/818bebeb63dd6bf5f4e07e145f6cdbace520a34c Added Reference https://git.kernel.org/stable/c/c96477e0cabf55bfbdf078078e9de1c8024f8060