Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f9ad21b90162baf1d78f8036ff3813c3ec1ac88e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f9ad21b90162baf1d78f8036ff3813c3ec1ac88e, 93a528f67ce5095bcab46a69839eca97f43dd352, 8fa8c2a22585fcb31dc605b91a67bbcca223fdd7

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to f9ad21b90162baf1d78f8036ff3813c3ec1ac88e, 93a528f67ce5095bcab46a69839eca97f43dd352 or 8fa8c2a22585fcb31dc605b91a67bbcca223fdd7.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ eb289a5f6cc668853f9b2ea6aca04afe58ed11c7, < f9ad21b90162baf1d78f8036ff3813c3ec1ac88e
Fixed in
  • f9ad21b90162baf1d78f8036ff3813c3ec1ac88e
LinuxLinuxAffected
  • ≥ eb289a5f6cc668853f9b2ea6aca04afe58ed11c7, < 93a528f67ce5095bcab46a69839eca97f43dd352
Fixed in
  • 93a528f67ce5095bcab46a69839eca97f43dd352
LinuxLinuxAffected
  • ≥ eb289a5f6cc668853f9b2ea6aca04afe58ed11c7, < 8fa8c2a22585fcb31dc605b91a67bbcca223fdd7
Fixed in
  • 8fa8c2a22585fcb31dc605b91a67bbcca223fdd7
LinuxLinuxAffected
  • =6.18
Fixed in–

Description

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)

References

Community reviews

Loading reviews…