CVE-2023-53514

5.5 MEDIUM 0.1% exploit odds Fix listed Other OS & kernel

What it is

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

At a glance

Exploitability: Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
Exploit odds: 0.1% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2025-10-01 12:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-11-05 21:17 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.1% in the next 30 days (EPSS).
Severity: 5.5 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2025-10-01 12:15 UTC
Last modified: 2026-11-05 21:17 UTC
Exploit probability: 0.1% · EPSS, next 30 days
Weakness: CWE-401
Record status: Analyzed

Affected

Linux Kernel < 6.1.28
Linux Kernel < 6.2.15
Linux Kernel < 6.3.2

Attack profile CVSS 3.1 · 5.5

Attack vector: Local
Complexity: Low
Privileges needed: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-53514.md and follow it. Check whether this project is affected by CVE-2023-53514. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record