CVE-2025-38036 json
drm/xe/vf: Perform early GT MMIO initialization to read GMDID
published last yr. modified 4mo ago also EUVD-2025-18616
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/vf: Perform early GT MMIO initialization to read GMDID
VFs need to communicate with the GuC to obtain the GMDID value and existing GuC functions used for that assume that the GT has it's MMIO members already setup. However, due to recent refactoring the gt->mmio is initialized later, and any attempt by the VF to use xe_mmio_read|write() from GuC functions will lead to NPD crash due to unset MMIO register address:
[] xe 0000:00:02.1: [drm] Running in SR-IOV VF mode [] xe 0000:00:02.1: [drm] GT0: sending H2G MMIO 0x5507 [] BUG: unable to handle page fault for address: 0000000000190240
Since we are already tweaking the id and type of the primary GT to mimic it's a Media GT before initializing the GuC communication, we can also call xe_gt_mmio_init() to perform early setup of the gt->mmio which will make those GuC functions work again.
Patch / fix
- Linux Linux 6.14.9, 6.15
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38036
- linux-aws-6.14 Ubuntu 24.04 LTS 6.14.0-1013.13~24.04.1
- linux-gcp-6.14 Ubuntu 24.04 LTS 6.14.0-1016.17~24.04.1
- linux-oem-6.14 Ubuntu 24.04 LTS 6.14.0-1012.12
- linux-riscv-6.14 Ubuntu 24.04 LTS 6.14.0-32.32.1~24.04.1
- linux-oracle-6.14 Ubuntu 24.04 LTS 6.14.0-1013.13~24.04.1
- linux-azure-nvidia-6.14 Ubuntu 24.04 LTS 6.14.0-1007.7
- linux-realtime-6.14 Ubuntu Pro Realtime 24.04 LTS 6.14.0-1012.12~24.04.1
ubuntu advisories UBUNTU-CVE-2025-38036
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2025-38036 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38036 updated cvss 5.5
kernel: Linux kernel: Denial of Service due to null pointer dereference in GT MMIO initialization for VFs
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
Sources
- CVE List CVE-2025-38036
- NVD CVE-2025-38036
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.