CVE-2026-90047

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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 ]

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 28, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

drm/xe: Don't hand out the flat CCS storage as usable VRAM - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/xe: Don't hand out the flat CCS storage as usable VRAM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/818bebeb63dd6bf5f4e07e145f6cdbace520a34c
generic

drm/xe: Don't hand out the flat CCS storage as usable VRAM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/348c3db4f1520d36764ac8cae2492f50599714f6

Vendor Advisories for CVE-2026-90047(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (177 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 77× 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-10-05 06:44 UTCEG score recompute
  2. 2026-10-05 06:44 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 18:09 UTCGHSA enrichment
  5. 2026-10-04 05:34 UTCGHSA enrichment
  6. 2026-10-03 16:59 UTCGHSA enrichment
  7. 2026-10-03 04:25 UTCEG score recompute
  8. 2026-10-03 04:25 UTCGHSA enrichment
  9. 2026-10-02 15:50 UTCGHSA enrichment
  10. 2026-10-02 03:16 UTCEG score recompute
  11. 2026-10-02 03:15 UTCGHSA enrichment
  12. 2026-10-01 19:51 UTCEPSS rescore
  13. 2026-10-01 14:39 UTCGHSA enrichment
  14. 2026-10-01 02:05 UTCEG score recompute
  15. 2026-10-01 02:05 UTCGHSA enrichment
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 13:28 UTCGHSA enrichment
  18. 2026-09-30 00:53 UTCEG score recompute
  19. 2026-09-30 00:53 UTCGHSA enrichment
  20. 2026-09-29 11:50 UTCGHSA enrichment
  21. 2026-09-28 23:15 UTCEG score recompute
  22. 2026-09-28 23:15 UTCGHSA enrichment
  23. 2026-09-28 19:01 UTCEG score recompute
  24. 2026-09-28 19:01 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 52 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 06:25 UTCGHSA enrichment
  3. 2026-09-27 17:50 UTCEG score recompute
  4. 2026-09-27 17:50 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 05:16 UTCGHSA enrichment
  7. 2026-09-26 16:41 UTCEG score recompute
  8. 2026-09-26 16:41 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 03:59 UTCEG score recompute
  11. 2026-09-26 03:59 UTCGHSA enrichment
  12. 2026-09-25 15:22 UTCGHSA enrichment
  13. 2026-09-25 02:47 UTCGHSA enrichment
  14. 2026-09-24 14:13 UTCEG score recompute
  15. 2026-09-24 14:12 UTCGHSA enrichment
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-24 01:20 UTCEG score recompute
  18. 2026-09-24 01:20 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 12:46 UTCGHSA enrichment
  21. 2026-09-23 00:11 UTCEG score recompute
  22. 2026-09-23 00:11 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 11:36 UTCGHSA enrichment
  25. 2026-09-21 23:01 UTCEG score recompute
  26. 2026-09-21 23:00 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 10:26 UTCGHSA enrichment
  29. 2026-09-20 21:52 UTCEG score recompute
  30. 2026-09-20 21:52 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 09:17 UTCGHSA enrichment
  33. 2026-09-19 20:39 UTCEG score recompute
  34. 2026-09-19 20:39 UTCGHSA enrichment
  35. 2026-09-19 08:04 UTCGHSA enrichment
  36. 2026-09-18 19:30 UTCEG score recompute
  37. 2026-09-18 19:30 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 06:54 UTCEG score recompute
  40. 2026-09-18 06:54 UTCGHSA enrichment
  41. 2026-09-17 19:32 UTCEPSS rescore
  42. 2026-09-17 18:19 UTCGHSA enrichment
  43. 2026-09-17 03:55 UTCEG score recompute
  44. 2026-09-17 03:55 UTCGHSA enrichment
  45. 2026-09-16 15:21 UTCEG score recompute
  46. 2026-09-16 15:21 UTCGHSA enrichment
  47. 2026-09-16 14:46 UTCEG score recompute▲ 7.80
  48. 2026-09-16 14:46 UTCGHSA enrichment
  49. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  50. 2026-09-16 11:21 UTCNVD update
  51. 2026-09-16 10:36 UTCEG score recompute
  52. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90047?
CVE-2026-90047 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe: Don't hand out the flat CCS storage as usable VRAM getflatccs_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…
When was CVE-2026-90047 disclosed?
CVE-2026-90047 was first published on September 16, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90047 actively exploited?
CVE-2026-90047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90047?
CVE-2026-90047 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90047?
No fix for CVE-2026-90047 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90047 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-90047

Explore →

Is Your Infrastructure Affected by CVE-2026-90047?

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