Answer in brief
CVE-2026-46224 records a Unknown severity vulnerability in drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=eb289a5f6cc668853f9b2ea6aca04afe58ed11c7 <f9ad21b90162baf1d78f8036ff3813c3ec1ac88e || >=eb289a5f6cc668853f9b2ea6aca04afe58ed11c7 <8fa8c2a22585fcb31dc605b91a67bbcca223fdd7 || >=eb289a5f6cc668853f9b2ea6aca04afe58ed11c7 <93a528f67ce5095bcab46a69839eca97f43dd352 | f9ad21b90162baf1d78f8036ff3813c3ec1ac88e, 8fa8c2a22585fcb31dc605b91a67bbcca223fdd7, 93a528f67ce5095bcab46a69839eca97f43dd352 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
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)
Quoted source text, attributed separately from HOL analysis.