linux: In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix memory leak of device names Th...
CVE-2023-53514 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-53514, released October 1, 2025. It is not reported as exploited. Patch Radar priority: Routine.
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().
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| linux · Debian 12.15 (bookworm) | 6.1.37-1 | DEBIAN-CVE-2023-53514 | Oct 1, 2025 |
| linux · Debian 13.5 (trixie) | 6.3.7-1 | DEBIAN-CVE-2023-53514 | Oct 1, 2025 |
| linux · Debian 14 | 6.3.7-1 | DEBIAN-CVE-2023-53514 | Oct 1, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.