Answer in brief
CVE-2023-53514 records a Medium severity (CVSS 5.5) vulnerability in gpu: host1x: Fix memory leak of device names. 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.
CVSS is 5.5. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8aa5bcb61612060429223d1fbb7a1c30a579fc1f <958c6cbc32996c375af42db96ceba021a1959899 || >=8aa5bcb61612060429223d1fbb7a1c30a579fc1f <dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c || >=8aa5bcb61612060429223d1fbb7a1c30a579fc1f <3ab0f5ddb761270b11d8c90b8550a59666cfc9bb || >=8aa5bcb61612060429223d1fbb7a1c30a579fc1f <55879dad0f3ae8468444b42f785ad79eac05fe5b | 958c6cbc32996c375af42db96ceba021a1959899, dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c, 3ab0f5ddb761270b11d8c90b8550a59666cfc9bb, 55879dad0f3ae8468444b42f785ad79eac05fe5b |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.