CVE-2026-43242
Memory Leak in Linux Kernel socinfo Driver
Publication date: 2026-05-06
Last updated on: 2026-05-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.19 (inc) to 6.19.6 (exc) |
| linux | linux_kernel | From 5.10.238 (inc) to 5.10.252 (exc) |
| linux | linux_kernel | From 5.15.185 (inc) to 5.15.202 (exc) |
| linux | linux_kernel | From 6.1.141 (inc) to 6.1.165 (exc) |
| linux | linux_kernel | From 6.12.31 (inc) to 6.12.75 (exc) |
| linux | linux_kernel | From 6.14.9 (inc) to 6.18.16 (exc) |
| linux | linux_kernel | From 6.6.93 (inc) to 6.6.128 (exc) |
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 related to the Linux kernel, specifically in the soc: ti: k3-socinfo component. During the probe process, a memory-mapped I/O (mmio) regmap is allocated but never freed if the probe fails. This causes a resource leak because the allocated regmap remains in memory instead of being released.
The fix involves switching to a device-managed allocator that automatically releases the regmap on probe failures (such as probe deferral) and when the driver is unbound, preventing the leak.
How can this vulnerability impact me? :
This vulnerability can lead to resource leaks in the Linux kernel, specifically memory leaks related to the regmap allocation during device probing. Over time, this could cause increased memory usage and potentially degrade system performance or stability if the leaked resources accumulate.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability involves a regmap memory leak in the ti k3-socinfo driver during probe failures. To mitigate this issue, update the Linux kernel to a version where this vulnerability is fixed, which includes switching to the device managed allocator for regmap to ensure proper cleanup on probe failure and driver unbind.