CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Don't allow evicting of BOs in same VM in array of VM binds
An array of VM binds can potentially evict other buffer objects (BOs)
within the same VM under certain conditions, which may lead to NULL
pointer dereferences later in the bind pipeline. To prevent this, clear
the allow_res_evict flag in the xe_bo_validate call.
v2:
- Invert polarity of no_res_evict (Thomas)
- Add comment in code explaining issue (Thomas)
(cherry picked from commit 8b9ba8d6d95fe75fed6b0480bb03da4b321bea08)
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel graphics-driver bug in drm/xe. Under specific VM bind handling, one buffer object can be evicted in a way that later causes a NULL pointer dereference. Business impact is most likely system instability or crash on affected hosts; the sources do not show data theft, privilege escalation, or active exploitation.
Executive priority
Handle through normal kernel patch management unless affected GPU-enabled Linux systems support critical operations. Escalate if crashes are observed or vendor advisories assign higher severity.
Technical view
The flaw is in drm/xe VM bind array processing. A VM bind array may evict other buffer objects in the same VM, leaving later bind pipeline logic exposed to NULL pointer dereferences. The kernel fix clears allow_res_evict during xe_bo_validate to prevent same-VM resource eviction in this path.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with the drm/xe driver path in use. The CVE data lists Linux kernel versions including 6.8, 6.17.5, and 6.18, but exact downstream distro status requires vendor package confirmation.
Exploitation context
The source bundle provides no KEV listing, exploit report, proof-of-concept, or attacker requirements. Treat active exploitation as unconfirmed. The described failure mode is a kernel NULL pointer dereference during graphics memory binding behavior.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or detailed impact beyond NULL pointer dereference is provided. Analysis should stay tied to the upstream fix and downstream kernel advisory mapping.
Mitigation direction
Review kernel vendor advisories for CVE-2025-40086 coverage.
Update to a kernel containing the referenced stable fixes.
Prioritize affected workstations or GPU-enabled Linux hosts.
Track distro backports rather than relying only on upstream version numbers.
If patching is delayed, review whether drm/xe is required on exposed hosts.
Validation and detection
Inventory Linux kernel versions across managed hosts.
Identify systems using the drm/xe driver path.
Compare installed kernel packages with vendor CVE advisories.
Confirm whether referenced stable commits are included or backported.
Monitor kernel logs for graphics-driver NULL dereference crashes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-40086 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 30, 2025, 09:47 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.