Answer in brief
CVE-2026-23026 records a Medium severity (CVSS 5.5) security vulnerability in CVE-2026-23026. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
Review the upstream advisory, identify the affected product in your inventory, and apply the vendor update when one is available.
Vulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-23026 as known exploited; continue to monitor the source for status changes. This is a product-level record in the current feed, not a package-level dependency mapping.
Affected software not mapped. Review the upstream record for vendor-specific product and version guidance.
Answer in brief
CVE-2026-23026 records a Medium severity (CVSS 5.5) security vulnerability in CVE-2026-23026. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
Review the upstream advisory, identify the affected product in your inventory, and apply the vendor update when one is available.
Vulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-23026 as known exploited; continue to monitor the source for status changes. This is a product-level record in the current feed, not a package-level dependency mapping.
Affected software not mapped. Review the upstream record for vendor-specific product and version guidance.
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.
Reported by NVD (nvd).
CVE-2026-23026 records a Medium severity (CVSS 5.5) security vulnerability in CVE-2026-23026. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
The source record does not mark it as known exploited.
Confirm whether the product or interface named by this advisory exists in your inventory.
HOL Guard can help your team monitor supply-chain activity while the upstream record is clarified.
Explore HOL GuardIn 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.
Reported by NVD (nvd).
CVE-2026-23026 records a Medium severity (CVSS 5.5) security vulnerability in CVE-2026-23026. The source record does not mark it as known exploited. No package mapping is present, so exposure must be confirmed against the affected product and deployment inventory.
The source record does not mark it as known exploited.
Confirm whether the product or interface named by this advisory exists in your inventory.
HOL Guard can help your team monitor supply-chain activity while the upstream record is clarified.
Explore HOL Guard