CVE-2026-23026
BaseFortify
Publication date: 2026-01-31
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 5.11 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.7 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.16 (inc) to 6.1.162 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.122 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.67 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.11.1 (inc) to 5.15.199 (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 a memory leak in the Linux kernel's dmaengine Qualcomm gpi driver, specifically in the function gpi_peripheral_config(). When the function attempts to reallocate memory using krealloc(), if krealloc() fails and returns NULL, the code incorrectly assigns NULL directly to gchan->config. This causes the original memory reference to be lost and the memory cannot be freed, resulting in a memory leak. The fix involves using a temporary variable to hold the result of krealloc() and only updating gchan->config if the allocation succeeds.
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel, which over time may cause increased memory usage and potentially degrade system performance or stability. In systems with limited memory or long uptime, this could result in resource exhaustion or crashes.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the memory leak in gpi_peripheral_config() has been fixed. The fix involves correcting the handling of krealloc() failure to prevent memory leaks. Applying the latest kernel patches or updates from your Linux distribution that address this issue is recommended.