Skip to main content

Linux EUVDEUVD-2026-15301

| CVE-2026-23337 MEDIUM
Memory Leak (CWE-401)
2026-03-25 Linux GHSA-5599-vj49-3fh3
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE
5.2 MEDIUM
qualitative
Red Hat
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
CVSS changed
Apr 23, 2026 - 21:27 NVD
5.5 (MEDIUM)
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
EUVD ID Assigned
Mar 25, 2026 - 10:45 euvd
EUVD-2026-15301
Analysis Generated
Mar 25, 2026 - 10:45 vuln.today
CVE Published
Mar 25, 2026 - 10:27 nvd
N/A

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

pinctrl: pinconf-generic: Fix memory leak in pinconf_generic_parse_dt_config()

In pinconf_generic_parse_dt_config(), if parse_dt_cfg() fails, it returns directly. This bypasses the cleanup logic and results in a memory leak of the cfg buffer.

Fix this by jumping to the out label on failure, ensuring kfree(cfg) is called before returning.

AnalysisAI

A memory leak vulnerability exists in the Linux kernel's pinctrl subsystem within the pinconf_generic_parse_dt_config() function. When the parse_dt_cfg() function fails, the code returns directly without executing cleanup logic, causing the cfg buffer to be leaked. This affects all Linux kernel versions containing the vulnerable pinctrl-generic code, and while the vulnerability itself does not enable direct code execution, it can lead to denial of service through memory exhaustion over time as the kernel gradually loses available memory.

Technical ContextAI

The vulnerability is located in the pinctrl (pin controller) subsystem's generic configuration parser, specifically in the pinconf_generic_parse_dt_config() function. The Linux kernel's pinctrl framework manages hardware pin configuration for various SoCs and devices. The root cause is a CWE-401 Missing Release of Memory after Effective Lifetime issue, where allocated memory (the cfg buffer) is not properly freed when an error condition occurs during device tree configuration parsing. The affected code path handles dynamic device tree configuration parsing for pin control hardware, and when parse_dt_cfg() encounters an error, it returns immediately without jumping to the cleanup label that would invoke kfree(cfg). This is a resource management flaw rather than an exploitable memory corruption issue.

RemediationAI

Update the Linux kernel to a version that includes the fix from commits 63ee429780a5d43b5b4406c6128109b0f47cf2f1 or 7a648d598cb8e8c62af3f0e020a25820a3f3a9a7 (available at https://git.kernel.org/stable/). Most Linux distributions will release patched kernels through their standard update channels. Users should apply kernel updates provided by their distribution vendor as part of routine security patching. For long-term support kernels, check your vendor's security advisory for the specific patched version. There are no known workarounds short of avoiding pinctrl device tree configuration parsing, which is impractical in production systems, so patching is the recommended remediation path.

Vendor StatusVendor

Debian

linux
Release Status Fixed Version Urgency
bullseye not-affected - -
bullseye (security) fixed 5.10.251-1 -
bookworm not-affected - -
bookworm (security) fixed 6.1.164-1 -
trixie not-affected - -
trixie (security) fixed 6.12.74-2 -
forky, sid fixed 6.19.8-1 -
(unstable) fixed 6.19.8-1 -

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

EUVD-2026-15301 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy