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)
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.32, 7.0.9
- CVEs
- CVE-2026-46224
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 05:26 UTC · Revision 1
Source evidence
drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure
core-osv · Original sourcePublished 28 May 2026, 09:40 UTC
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)
osv:CVE-2026-46224
Kernel
Fixed versions: 6.18.32, 7.0.9
Complete source record
{
"id": "d4b806c7b2d2c063d6d39873920cffaff6d70dc9017ef0a27023b58e97b8ad78",
"url": "https://osv.dev/vulnerability/CVE-2026-46224",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure",
"summary": "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)",
"evidence": "osv:CVE-2026-46224",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.32",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-46224",
"aliases": [
"CVE-2026-46224"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "eb289a5f6cc668853f9b2ea6aca04afe58ed11c7"
},
{
"fixed": "f9ad21b90162baf1d78f8036ff3813c3ec1ac88e"
},
{
"fixed": "8fa8c2a22585fcb31dc605b91a67bbcca223fdd7"
},
{
"fixed": "93a528f67ce5095bcab46a69839eca97f43dd352"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46224.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.18.0"
},
{
"fixed": "6.18.32"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46224.json"
}
}
],
"modified": "2026-10-28T02:30:42.982931683Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/8fa8c2a22585fcb31dc605b91a67bbcca223fdd7",
"https://git.kernel.org/stable/c/93a528f67ce5095bcab46a69839eca97f43dd352",
"https://git.kernel.org/stable/c/f9ad21b90162baf1d78f8036ff3813c3ec1ac88e",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46224.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-46224",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46224.json"
}
},
"related_cves": [
{
"value": "CVE-2026-46224",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 510703,
"published_at": "2026-05-28T09:40:42.819+00:00"
}