Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23026, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 4532f18e4ab36def1f55cd936d0fc002b2ce34c2
    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 694ab1f6f16cb69f7c5ef2452b22ba7b00a3c7c7
    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 6bf4ef078fd11910988889a6c0b3698d2e0c89af
    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 01b1d781394fc9b83015e3a3cd46b17bda842bd8
    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 55a67ba5ac4cebfd54cc8305d4d57a0f1dfe6a85
    • affected 5d0c3533a19f48e5e7e73806a3e4b29cd4364130 – < 3f747004bbd641131d9396d87b5d2d3d1e182728
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.67 – ≤ 6.12.*
    • unaffected 6.18.7 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23026 badge
[![CVE-2026-23026](https://cveledger.app/badge/CVE-2026-23026.svg)](https://cveledger.app/cve/CVE-2026-23026)

Record last updated .