CVE-2026-46030

EDAC/versalnet: Fix device_node leak in mc_probe()

Published May 27, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

EDAC/versalnet: Fix device_node leak in mc_probe()

of_parse_phandle() returns a device_node reference that must be released with
of_node_put(). The original code never freed r5_core_node on any exit path,
causing a memory leak.

Fix this by using the automatic cleanup attribute __free(device_node) which
ensures of_node_put() is called when the variable goes out of scope.

Analysis

AI-generated

Technical impact

In the Linux kernel, a device_node reference returned by of_parse_phandle() is never freed in the EDAC/versalnet driver. The reference r5_core_node remains allocated on all exit paths, creating a memory leak. Over time, repeated invocations could accumulate unused memory, degrading system performance and potentially exhausting available memory, which may affect stability and availability.

Affected Systems

The vulnerability affects the Linux kernel, specifically the VersalNet EDAC driver that handles hardware error detection on Versal Net devices. Any system running a kernel build that contains this driver and does not include the patch will be susceptible.

Risk and Exploitability

The CVSS score of 5.5 indicates a moderate severity, while the EPSS score of <1% suggests a low likelihood of exploitation. This issue is not listed in the CISA KEV catalog. The risk remains primarily internal: a long‑running device that loads and unloads the EDAC/versalnet driver repeatedly could accumulate memory usage, but there is no known external attack vector or privilege escalation from the leak. Consequently, exploitation likelihood is considered low and the impact remains moderate, limited to resource exhaustion.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a kernel version that includes the mc_probe() memory leak fix
  • If a kernel update is not immediately available, apply the patch from the provided kernel commits (17e1369, 5c709b3, b6e6135) and rebuild the kernel
  • If the patch cannot be applied, disable the EDAC/versalnet driver or limit its use to prevent prolonged memory accumulation

Generated by OpenCVE AI on June 18, 2026 at 02:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8488-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8489-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8488-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8507-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-401
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-401
Type Values Removed Values Added
Weaknesses CWE-401
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: EDAC/versalnet: Fix device_node leak in mc_probe() of_parse_phandle() returns a device_node reference that must be released with of_node_put(). The original code never freed r5_core_node on any exit path, causing a memory leak. Fix this by using the automatic cleanup attribute __free(device_node) which ensures of_node_put() is called when the variable goes out of scope.
Title EDAC/versalnet: Fix device_node leak in mc_probe()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

  • CWE-911

    Improper Update of Reference Count

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jun 14, 2026, 5:49 PM
Reserved
May 13, 2026, 3:03 PM
Status
Analyzed
Published
May 27, 2026, 2:17 PM
Modified
Jun 17, 2026, 10:52 AM
Severity
Public date
May 27, 2026, 12:00 AM