https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 06:35:14 +0000 https://vulnerability.circl.lu/vuln/cve-2026-64328 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Fix DMA fence leak</p> <p>In ffs_dmabuf_transfer(), a ffs_dma_fence object is kmalloc&#39;d, with the underlying dma_fence later initialized by dma_fence_init(), which sets its kref counter to 1. Then, dma_resv_add_fence() gets a second reference, and a pointer to the ffs_dma_fence is passed as the usb_request&#39;s &#34;context&#34; field.</p> <p>The dma-resv mechanism will manage the second reference, but the first reference is never properly released; the ffs_dmabuf_cleanup() function decreases the reference count, but only to balance with the reference grab in ffs_dmabuf_signal_done().</p> <p>The code will then slowly leak memory as more ffs_dma_fence objects are created without being ever freed.</p> <p>Address this issue by transferring ownership of the fence to the DMA reservation object, by calling dma_fence_put() right after dma_resv_add_fence(). The ffs_dma_fence then gets properly discarded after being signalled.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Fix DMA fence leak</p> <p>In ffs_dmabuf_transfer(), a ffs_dma_fence object is kmalloc&#39;d, with the underlying dma_fence later initialized by dma_fence_init(), which sets its kref counter to 1. Then, dma_resv_add_fence() gets a second reference, and a pointer to the ffs_dma_fence is passed as the usb_request&#39;s &#34;context&#34; field.</p> <p>The dma-resv mechanism will manage the second reference, but the first reference is never properly released; the ffs_dmabuf_cleanup() function decreases the reference count, but only to balance with the reference grab in ffs_dmabuf_signal_done().</p> <p>The code will then slowly leak memory as more ffs_dma_fence objects are created without being ever freed.</p> <p>Address this issue by transferring ownership of the fence to the DMA reservation object, by calling dma_fence_put() right after dma_resv_add_fence(). The ffs_dma_fence then gets properly discarded after being signalled.</p> https://vulnerability.circl.lu/vuln/cve-2026-64328