LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46224: drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo is not freed. Add xe_bo_free(storage) before returning the error. xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own error paths. Otherwise, since xe_gem_prime_import() cannot distinguish whether the failure originated from xe_dma_buf_init_obj() or from xe_bo_init_locked(), it cannot safely decide whether the bo should be freed. Add comments documenting the ownership semantics: on success, ownership of storage is transferred to the returned drm_gem_object; on failure, storage is freed before returning. v2: Add comments to explain the free logic. (cherry picked from commit 78a6c5f899f22338bbf48b44fb8950409c5a69b9)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a resource leak in the Intel Xe graphics driver error path. If an allocation fails during DMA-BUF object initialization, a preallocated buffer object is not released. The documented impact is incomplete; the practical business concern is possible kernel memory/resource pressure on affected systems using this driver.

Executive priority

Treat as a routine kernel maintenance item unless affected GPU hosts are multi-tenant or resource constrained. There is no sourced evidence of exploitation, but kernel resource leaks can affect availability when triggerable.

Technical view

In drm/xe, xe_dma_buf_init_obj() failed to free the preallocated storage bo when drm_gpuvm_resv_object_alloc() returned an error. The fix adds xe_bo_free(storage) and documents ownership transfer semantics between storage, drm_gem_object, and failure paths.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the drm/xe driver path present and reachable. The source bundle does not prove remote exposure, privilege requirements, or whether normal users can reliably trigger the failing allocation path.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The source material describes a memory/resource leak on an allocation-failure path, not a code execution or data disclosure primitive.

Researcher notes

The key uncertainty is reachability. The CVE text identifies the flawed ownership cleanup but does not state trigger prerequisites, user privileges, crash behavior, or reproducibility. Validate by code review and vendor package mapping, not by assuming broad exploitability.

Mitigation direction

  • Apply Linux kernel stable updates containing the referenced drm/xe fixes.
  • Check distribution advisories for exact affected and fixed package versions.
  • Prioritize systems using Intel Xe graphics or exposing DRM devices to workloads.
  • Review unnecessary access to GPU or DRM devices in shared environments.

Validation and detection

  • Inventory kernel versions against vendor fixed-version guidance.
  • Confirm whether drm/xe is present and used on affected hosts.
  • Review package changelogs for the referenced stable commit IDs.
  • Monitor for kernel memory pressure on systems using the Xe driver.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2026-46224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxeb289a5f6cc668853f9b2ea6aca04afe58ed11c7, eb289a5f6cc668853f9b2ea6aca04afe58ed11c7, eb289a5f6cc668853f9b2ea6aca04afe58ed11c7unaffected
LinuxLinux6.18, 0, 6.18.32, 7.0.9, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.