LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53514: 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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53514 is a Linux kernel resource-management bug in the gpu host1x area. Device names allocated during setup may not be freed correctly during module unloading. The available sources describe a memory leak fix, not code execution, privilege escalation, or data theft.

Executive priority

Handle through normal kernel patch management, with higher priority for systems using host1x GPU functionality. Current evidence does not support emergency treatment, but incomplete severity data warrants tracking until vendor advisories are reviewed.

Technical view

The fix changes host1x device cleanup so successfully added devices are unregistered and not-added devices only drop their reference. It also adds an empty release function to avoid device_release warnings. Sources identify affected Linux kernel ranges but provide no CVSS, CWE, exploit details, or operational impact metrics.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions where the host1x GPU driver path is present. The source bundle lists Linux as affected and provides kernel ranges, but does not identify distributions, hardware platforms, or package names.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. No public exploitability assessment is provided. Treat this as a kernel stability and resource-leak issue unless vendor guidance adds stronger impact details.

Researcher notes

The available record is sparse: no CVSS, CWE, exploit status, distribution mapping, or detailed threat model. The change is centered on device lifetime cleanup and reference handling during module unload, suggesting resource leakage rather than direct attacker-controlled compromise.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize systems using host1x GPU functionality.
  • Plan normal kernel reboot procedures after updating.
  • Monitor vendor notes for any revised severity or impact.

Validation and detection

  • Inventory Linux kernel versions against the affected ranges.
  • Confirm whether host1x GPU support is enabled or present.
  • Review kernel package changelogs for the referenced fix commits.
  • Verify updated systems run a fixed kernel after reboot.
  • Track exceptions where vendor guidance is unavailable.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53514 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8aa5bcb61612060429223d1fbb7a1c30a579fc1f, 8aa5bcb61612060429223d1fbb7a1c30a579fc1f, 8aa5bcb61612060429223d1fbb7a1c30a579fc1f, 8aa5bcb61612060429223d1fbb7a1c30a579fc1funaffected
LinuxLinux6.0, 0, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.