CVE-2023-53514

gpu: host1x: Fix memory leak of device names

MEDIUM
5.5
CVSS Score
Published: October 1, 2025 at 11:46 AM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.286.0 ≤ v < 6.2.156.0 ≤ v < 6.3.26.0 ≤ v < 6.46.2 ≤ v < 6.2.156.3 ≤ v < 6.3.26.08aa5bcb61612060429223d1fbb7a1c30a579fc1f
Vendor states this is fixed in 3ab0f5ddb761270b11d8c90b8550a59666cfc9bb (fixed)
Vendor states this is fixed in 55879dad0f3ae8468444b42f785ad79eac05fe5b (fixed)
Vendor states this is fixed in 958c6cbc32996c375af42db96ceba021a1959899 (fixed)
Vendor states this is fixed in dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card