VYPR
Unrated severityNVD Advisory· Published Jan 31, 2026· Updated Apr 15, 2026

CVE-2026-23033

CVE-2026-23033

Description

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: omap-dma: fix dma_pool resource leak in error paths

The dma_pool created by dma_pool_create() is not destroyed when dma_async_device_register() or of_dma_controller_register() fails, causing a resource leak in the probe error paths.

Add dma_pool_destroy() in both error paths to properly release the allocated dma_pool resource.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A resource leak in the Linux kernel's omap-dma driver where a dma_pool is not freed on probe failure, fixed by adding dma_pool_destroy() calls.

Vulnerability

CVE-2026-23033 is a resource leak vulnerability in the Linux kernel's omap-dma DMA engine driver. The root cause is that the dma_pool created via dma_pool_create() during driver probe is not destroyed when either dma_async_device_register() or of_dma_controller_register() fails. This leaves the allocated DMA pool memory unreleased, leading to a memory leak in the probe error paths [1][2][3].

Exploitation

This vulnerability is triggered during the driver initialization (probe) phase. An attacker would need to cause the probe to fail after the pool is created but before the registration calls succeed. This could be achieved by manipulating device tree entries or hardware configuration to force-unbind scenarios, though the exact attack surface depends on system configuration. No authentication is required, as the driver probe occurs in kernel context during device enumeration.

Impact

An attacker who can repeatedly trigger probe failures could exhaust kernel memory by leaking DMA pool allocations, potentially leading to denial of service (DoS). The leak is per-failure, so sustained exploitation could degrade system stability. There is no evidence of code execution or privilege escalation from this bug.

Mitigation

The fix adds dma_pool_destroy() calls in both error paths, both error paths, ensuring the pool is released on failure. The patch [1][2][3]. The fix has been merged into the stable kernel tree. Users should update to a kernel version containing the commit.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

7

News mentions

0

No linked articles in our index yet.