CVE-2026-46221
Received Received - Intake
EDAC/versalnet Memory Leak Fix in Linux Kernel

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: EDAC/versalnet: Fix device name memory leak The device name allocated via kzalloc() in init_one_mc() is assigned to dev->init_name but never freed on the normal removal path. device_register() copies init_name and then sets dev->init_name to NULL, so the name pointer becomes unreachable from the device. Thus leaking memory. Use a stack-local char array instead of using kzalloc() for name.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
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 related to the EDAC/versalnet driver. Specifically, the device name allocated using kzalloc() in the function init_one_mc() is assigned to dev->init_name but is never freed during the normal device removal process. Since device_register() copies the init_name and then sets dev->init_name to NULL, the original allocated memory becomes unreachable and is therefore leaked.

The fix involves using a stack-local character array instead of dynamically allocating memory with kzalloc() for the device name, preventing the memory leak.


How can this vulnerability impact me? :

This vulnerability can lead to a memory leak in the Linux kernel, which means that memory allocated for device names is not properly freed when devices are removed. Over time, this can cause increased memory usage and potentially degrade system performance or stability, especially on systems where devices are frequently added and removed.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability involves a memory leak in the Linux kernel's EDAC/versalnet driver due to improper freeing of device name memory.

To mitigate this vulnerability, update your Linux kernel to a version where this issue is fixed, as the fix involves changing the allocation method for the device name from kzalloc() to a stack-local char array.


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