In the Linux kernel, the following vulnerability has been resolved: iio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf()… (CVE-2026-63929)
A vulnerability in the Linux kernel's Industrial I/O (iio) buffer subsystem caused a memory leak due to a missing release of a DMA fence reference in the iio_buffer_enqueue_dmabuf() function. This leak results from the function not calling dma_fence_put() after dma_resv_add_fence(), causing permanent allocation growth. The issue was fixed by ensuring the DMA fence reference is properly released, preventing the leak.
AI Analysis
Technical Summary
The Linux kernel's iio_buffer_enqueue_dmabuf() function allocates a DMA fence structure with an initial reference count of 1, then dma_resv_add_fence() adds a second reference. However, on successful execution, the function returns without releasing the initial reference, causing a permanent memory leak of kmalloc-128 allocations. This leak accumulates rapidly under typical usage scenarios, as confirmed by slab growth and ftrace analysis showing dma_fence_destroy was never triggered. The fix involves calling dma_fence_put() after dma_resv_add_fence() to transfer ownership correctly and allow proper cleanup.
Potential Impact
The vulnerability causes a memory leak in the kernel's iio buffer subsystem, leading to continuous growth of allocated memory (kmalloc-128 slabs) during normal operation. This can degrade system performance or stability over time due to resource exhaustion. There is no indication of direct code execution or privilege escalation from this leak.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call dma_fence_put() after dma_resv_add_fence(), ensuring proper release of the DMA fence reference and preventing the memory leak. Users should apply the official kernel update containing this fix. Patch status is not explicitly stated in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: iio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf()… (CVE-2026-63929)
Description
A vulnerability in the Linux kernel's Industrial I/O (iio) buffer subsystem caused a memory leak due to a missing release of a DMA fence reference in the iio_buffer_enqueue_dmabuf() function. This leak results from the function not calling dma_fence_put() after dma_resv_add_fence(), causing permanent allocation growth. The issue was fixed by ensuring the DMA fence reference is properly released, preventing the leak.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's iio_buffer_enqueue_dmabuf() function allocates a DMA fence structure with an initial reference count of 1, then dma_resv_add_fence() adds a second reference. However, on successful execution, the function returns without releasing the initial reference, causing a permanent memory leak of kmalloc-128 allocations. This leak accumulates rapidly under typical usage scenarios, as confirmed by slab growth and ftrace analysis showing dma_fence_destroy was never triggered. The fix involves calling dma_fence_put() after dma_resv_add_fence() to transfer ownership correctly and allow proper cleanup.
Potential Impact
The vulnerability causes a memory leak in the kernel's iio buffer subsystem, leading to continuous growth of allocated memory (kmalloc-128 slabs) during normal operation. This can degrade system performance or stability over time due to resource exhaustion. There is no indication of direct code execution or privilege escalation from this leak.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call dma_fence_put() after dma_resv_add_fence(), ensuring proper release of the DMA fence reference and preventing the memory leak. Users should apply the official kernel update containing this fix. Patch status is not explicitly stated in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7xv7-rch9-q9hw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63929"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f268
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:07:58 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.