CVE-2022-50734
Unknown Unknown - Not Provided
Memory Leak in Linux Kernel nvmem_register() Function

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: nvmem: core: Fix memleak in nvmem_register() dev_set_name will alloc memory for nvmem->dev.kobj.name in nvmem_register, when nvmem_validate_keepouts failed, nvmem's memory will be freed and return, but nobody will free memory for nvmem->dev.kobj.name, there will be memleak, so moving nvmem_validate_keepouts() after device_register() and let the device core deal with cleaning name in error cases.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a memory leak in the Linux kernel's nvmem subsystem. Specifically, when the function nvmem_register is called, memory is allocated for nvmem->dev.kobj.name using dev_set_name. If the nvmem_validate_keepouts function fails, the memory allocated for nvmem is freed, but the memory allocated for nvmem->dev.kobj.name is not freed, causing a memory leak. The fix involved moving the call to nvmem_validate_keepouts after device_register so that the device core can properly handle cleaning up the name memory in error cases.


How can this vulnerability impact me? :

This vulnerability can lead to a memory leak in the Linux kernel, which over time could cause increased memory usage and potentially degrade system performance or stability if the leaked memory accumulates.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart