CVE-2026-23337: pinctrl: pinconf-generic: Fix memory leak in pinconf_generic_parse_dt_config()
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23337 is a Linux kernel memory leak in pin control configuration parsing. On a specific failure path, allocated memory is not freed. The public bundle does not provide CVSS, CWE, exploitability, or real-world impact evidence, so urgency should be based on kernel exposure and vendor guidance.
Executive priority
Treat as a routine kernel maintenance item unless vendor guidance raises severity. There is no provided evidence of exploitation or major business impact, but unpatched kernels should still be updated through normal change windows.
Technical view
In pinconf_generic_parse_dt_config(), a parse_dt_cfg() failure returns directly and skips cleanup of the cfg buffer. The referenced fix changes failure handling to jump to the cleanup label so kfree(cfg) runs before return.
Likely exposure
Exposure is limited to Linux systems running affected kernel code. The bundle lists Linux and version identifiers including 6.19, 6.19.7, 7.0, and kernel commits, but exact range semantics are incomplete here.
Exploitation context
No active exploitation is stated in the provided sources, and KEV is false. The sources describe a memory leak on an error path, not a demonstrated remote or local exploit path.
Researcher notes
The record is narrowly scoped to a memory leak in pinctrl generic device-tree config parsing. The bundle lacks CVSS, CWE, trigger conditions, privilege context, and affected range clarity, so validation should rely on vendor kernel advisories and source-level patch presence.
Mitigation direction
Check Linux distribution or kernel vendor advisories for CVE-2026-23337.
Update to a kernel build containing the referenced stable fixes.
Prioritize embedded or device-tree-heavy systems if they run affected kernel versions.
Track vendor severity once CVSS or downstream advisories become available.
Validation and detection
Inventory Linux kernel versions and downstream vendor build identifiers.
Compare deployed kernels against vendor advisories and referenced stable commits.
Review SBOM or image manifests for affected Linux kernel packages.
Confirm patched builds include cleanup for the cfg buffer failure path.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23337 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 25, 2026, 10:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.