Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53514gpu: host1x: Fix memory leak of device names

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53514, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 8aa5bcb61612060429223d1fbb7a1c30a579fc1f – < 958c6cbc32996c375af42db96ceba021a1959899
    • affected 8aa5bcb61612060429223d1fbb7a1c30a579fc1f – < dba1aeaaf3d0e2f996cb0a5609e5e85ecf405a5c
    • affected 8aa5bcb61612060429223d1fbb7a1c30a579fc1f – < 3ab0f5ddb761270b11d8c90b8550a59666cfc9bb
    • affected 8aa5bcb61612060429223d1fbb7a1c30a579fc1f – < 55879dad0f3ae8468444b42f785ad79eac05fe5b
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53514 badge
[![CVE-2023-53514](https://cveledger.app/badge/CVE-2023-53514.svg)](https://cveledger.app/cve/CVE-2023-53514)

Record last updated .