LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23026: dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux Qualcomm GPI DMA driver error can leak kernel memory when resizing an existing configuration fails. Repeated triggering could consume resources and affect availability, but the supplied sources do not quantify impact, reachability, or attack prerequisites. No confidentiality or code-execution impact is established.

Executive priority

Treat as a targeted availability concern, not an established emergency. Identify exposed Qualcomm-based systems and apply supported kernel updates during normal expedited maintenance. Raise priority where memory exhaustion would disrupt safety-critical, industrial, or high-availability operations.

Technical view

In gpi_peripheral_config(), krealloc() was assigned directly to gchan->config. If allocation failed, NULL replaced the original pointer, leaving its allocation unreachable. The stable fixes preserve the result in a temporary variable and update gchan->config only after successful allocation. Static analysis and code review found the defect.

Likely exposure

Exposure is limited to Linux systems using the Qualcomm GPI DMA driver and an affected kernel revision. The record lists affected versions from 5.11 through specified stable releases and 6.19, but does not describe configuration requirements, reachable interfaces, or affected downstream distributions and appliances.

Exploitation context

The supplied record says the issue was found through static analysis and code review. It is not in KEV, and no cited evidence establishes active exploitation or a public exploit. Triggerability and the allocation-failure conditions required to produce meaningful resource exhaustion remain unspecified.

Researcher notes

The defect is a failed-reallocation pointer-loss pattern. The sources establish a leak but provide no CVSS score, CWE assignment, proof of attacker-controlled reachability, leak rate, or demonstrated denial of service. The duplicated commit-based version data and unusual listed version “0” warrant confirmation against stable-tree and downstream records.

Mitigation direction

  • Install a vendor-supported kernel update containing the applicable stable fix.
  • Check distribution or appliance advisories for backported fixes and exact affected package versions.
  • Prioritize systems that enable or actively use the Qualcomm GPI DMA driver.
  • Use vendor guidance if an immediate kernel update is unavailable.

Validation and detection

  • Inventory kernel versions on systems using Qualcomm hardware or the GPI DMA driver.
  • Compare deployed kernel builds with the CVE record and downstream vendor advisories.
  • Confirm the applicable stable fix commit is present or backported.
  • Monitor affected systems for unexplained kernel memory growth or availability degradation after relevant device activity.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23026 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5d0c3533a19f48e5e7e73806a3e4b29cd4364130, 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, 5d0c3533a19f48e5e7e73806a3e4b29cd4364130, 5d0c3533a19f48e5e7e73806a3e4b29cd4364130unaffected
LinuxLinux5.11, 0, 5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.