VDB

CVE-2025-38036

CVE-2025-38036 PUBLISHED

drm/xe/vf: Perform early GT MMIO initialization to read GMDID

Reported by linux · Published June 18, 2025

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.

EPSS 0.16% · 5.5th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
linux-gcp-6.12Chainguard6.12.80-r0

Risk scores

EPSS Score
0.16%
5.5th percentile

Affected products

VendorProductVersions
LinuxLinuxdd08ebf6c3525a7ea2186e636df064ea47281987, dd08ebf6c3525a7ea2186e636df064ea47281987
LinuxLinux6.8, 0, 6.14.9
chainguardlinux-gcp-6.120
linuxlinux_kernel6.8, 6.8
chainguardlinux-vmware-6.120
chainguardlinux-aws-6.120
chainguardlinux-azure-6.120
LinuxLinux6.14.9, 6.15, 6.8
chainguardlinux-qemu-6.120

Timeline

  • Jun 17, 2025 CVE Published
  • Jun 18, 2025 EPSS Score (30 in total, the first dated here)
  • Jun 18, 2025 Coalition ESS Score (9 in total, the first dated here)
  • Dec 15, 2025 Security Advisory (276 in total, the first dated here)
  • Apr 29, 2026 Distribution Patch (264 in total, the first dated here)
  • Oct 13, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-38036
vulnetix vdb fixes CVE-2025-38036

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38036/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›