CVE-2026-23337
Memory Leak in Linux Kernel pinctrl pinconf-generic Component
Publication date: 2026-03-25
Last updated on: 2026-04-23
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.19.1 (inc) to 6.19.7 (exc) |
| linux | linux_kernel | 6.19 |
Helpful Resources
Exploitability
| 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
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's pinctrl subsystem, specifically in the pinconf-generic component. The issue occurs in the function pinconf_generic_parse_dt_config(), where if the helper function parse_dt_cfg() fails, the code returns immediately without executing the cleanup logic. This causes the allocated memory buffer (cfg) to not be freed, resulting in a memory leak.
How can this vulnerability impact me? :
The impact of this vulnerability is a memory leak in the Linux kernel. Over time, repeated triggering of this issue could cause increased memory usage, potentially leading to reduced system performance or stability issues. However, there is no indication of direct exploitation beyond the memory leak itself.