gpu: host1x: Fix memory leak of device names
In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names The device names allocated by dev_set_name() need be freed before module unloading, but they can not be freed because the kobject's refcount which was set in device_initialize() has not be decreased to 0. As comment of device_add() says, if it fails, use only put_device() drop the refcount, then the name will be freed in kobejct_cleanup(). device_del() and put_device() can be replaced with device_unregister(), so call it to unregister the added successfully devices, and just call put_device() to the not added device. Add a release() function to device to avoid null release() function WARNING in device_release(), it's empty, because the context devices are freed together in host1x_memory_context_list_free().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.28, 6.2.15, 6.3.2
- CVEs
- CVE-2023-53514
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 18:05 UTC · Revision 1
Source evidence
gpu: host1x: Fix memory leak of device names
core-osv · Original sourcePublished 1 Oct 2025, 11:46 UTC
In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names The device names allocated by dev_set_name() need be freed before module unloading, but they can not be freed because the kobject's refcount which was set in device_initialize() has not be decreased to 0. As comment of device_add() says, if it fails, use only put_device() drop the refcount, then the name will be freed in kobejct_cleanup(). device_del() and put_device() can be replaced with device_unregister(), so call it to unregister the added successfully devices, and just call put_device() to the not added device. Add a release() function to device to avoid null release() function WARNING in device_release(), it's empty, because the context devices are freed together in host1x_memory_context_list_free().
osv:CVE-2023-53514
Kernel
Fixed versions: 6.1.28, 6.2.15, 6.3.2
Complete source record
{
"id": "7c4003a66a0d9885d31ff8db3b6f7d2ad1efb0b53e2968fc113834c9d98c14a3",
"url": "https://osv.dev/vulnerability/CVE-2023-53514",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "gpu: host1x: Fix memory leak of device names",
"summary": "In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names The device names allocated by dev_set_name() need be freed before module unloading, but they can not be freed because the kobject's refcount which was set in device_initialize() has not be decreased to 0. As comment of device_add() says, if it fails, use only put_device() drop the refcount, then the name will be freed in kobejct_cleanup(). device_del() and put_device() can be replaced with device_unregister(), so call it to unregister the added successfully devices, and just call put_device() to the not added device. Add a release() function to device to avoid null release() function WARNING in device_release(), it's empty, because the context devices are freed together in host1x_memory_context_list_free().",
"evidence": "osv:CVE-2023-53514",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.28",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.15",
"evidence": "/affected/1/ranges"
},
{
"value": "6.3.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2023-53514",
"aliases": [
"CVE-2023-53514"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8aa5bcb61612060429223d1fbb7a1c30a579fc1f"
},
{
"fixed": "958c6cbc32996c375af42db96ceba021a1959899"
},
{
"fixed": "dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c"
},
{
"fixed": "3ab0f5ddb761270b11d8c90b8550a59666cfc9bb"
},
{
"fixed": "55879dad0f3ae8468444b42f785ad79eac05fe5b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53514.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.1.28"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.15"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.3.0"
},
{
"fixed": "6.3.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53514.json"
}
}
],
"modified": "2026-10-28T02:30:22.224797005Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3ab0f5ddb761270b11d8c90b8550a59666cfc9bb",
"https://git.kernel.org/stable/c/55879dad0f3ae8468444b42f785ad79eac05fe5b",
"https://git.kernel.org/stable/c/958c6cbc32996c375af42db96ceba021a1959899",
"https://git.kernel.org/stable/c/dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53514.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53514",
"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/2023/53xxx/CVE-2023-53514.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53514",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 488008,
"published_at": "2025-10-01T11:46:02.393+00:00"
}