dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 · < 3f747004bbd641131d9396d87b5d2d3d1e182728| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Qualcomm GPI DMA engine can leak memory in gpi_peripheral_config() if a memory reallocation fails. The input does not establish whether an attacker can trigger this condition or specify access or user-interaction requirements.
Engineers running Linux kernels with the Qualcomm GPI DMA engine should check their deployments; affected versions were not specified.