Bug 2435656 (CVE-2026-23026) - CVE-2026-23026 kernel: dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config()
Summary: CVE-2026-23026 kernel: dmaengine: qcom: gpi: Fix memory leak in gpi_periphera...
Keywords:
Status: NEW
Alias: CVE-2026-23026
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-31 12:02 UTC by OSIDB Bzimport
Modified: 2026-02-02 10:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-01-31 12:02:06 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.