CVE-2026-23033: dmaengine: omap-dma: fix dma_pool resource leak in error paths
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: omap-dma: fix dmapool resource leak in error paths
The dmapool created by dmapoolcreate() is not destroyed when dmaasyncdeviceregister() or ofdmacontrollerregister() fails, causing a resource leak in the probe error paths.
Add dmapooldestroy() in both error paths to properly release the allocated dmapool resource.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Compensating control
Add dma_pool_destroy() in both probe error paths when dma_async_device_register() or of_dma_controller_register() fails, to release the dma_pool created by dma_pool_create().
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23033?
CVE-2026-23033 has a severity level that depends on the specific context of the affected software configurations but is important to address to avoid resource leaks.
How do I fix CVE-2026-23033?
To fix CVE-2026-23033, ensure that the dma_pool created by dma_pool_create() is properly destroyed in all error paths of the relevant functions.
What systems are affected by CVE-2026-23033?
CVE-2026-23033 affects the Linux kernel, particularly systems that utilize the omap-dma engine.
What are the potential consequences of CVE-2026-23033 if left unpatched?
If left unpatched, CVE-2026-23033 could lead to resource leaks that may degrade system performance or cause instability.
How can I verify if my system is impacted by CVE-2026-23033?
You can verify if your system is impacted by CVE-2026-23033 by checking the version of the Linux kernel and any related configurations that utilize the omap-dma engine.