# CVE-2026-90047: drm/xe: Don't hand out the flat CCS storage as usable VRAM CVE-2026-90047 is fixed in 12 products on 1 platform, first by DEBIAN-CVE-2026-90047, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-90047 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 16, 2026 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-90047 ## 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 ] ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.84.1.150700.17.47.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7-RT_Update_21 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4640-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4640-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7_Update_22 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | linux Debian 14 | 7.2.6-1 | [DEBIAN-CVE-2026-90047](https://patchblox.com/security/data/fix/linux/debian-cve-2026-90047.md) | Sep 23, 2026 | --- Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.