CVE-2026-46221

Analyzed Analyzed - Analysis Complete

EDAC/versalnet Memory Leak Fix in Linux Kernel

Publication date: 2026-05-28

Last updated on: 2026-06-10

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-06-10

Generated

2026-07-08

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-06

NVD

CVE-2026-46221

EUVD

EUVD-2026-32848

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.18 (inc) to 6.18.32 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.9 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-401	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Attack-Flow Graph

Mitigation Strategies

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.

Executive Summary

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.

Impact Analysis

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.

Compliance Impact

The vulnerability described is a memory leak in the Linux kernel related to device name allocation and freeing. There is no information provided about any impact on data privacy, data protection, or regulatory compliance such as GDPR or HIPAA.

Memory leaks typically affect system stability and resource usage rather than compliance with data protection standards.

Hi! I’m here to help you understand CVE-2026-46221. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70