CVE-2026-64328 Details
Description
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix DMA fence leak In ffs_dmabuf_transfer(), a ffs_dma_fence object is kmalloc'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's "context" field. 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(). The code will then slowly leak memory as more ffs_dma_fence objects are created without being ever freed. 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.
A memory leak vulnerability has been identified in the Linux kernel's USB gadget FunctionFS component, specifically within the DMABUF transfer handling. The issue arises because a ffs_dma_fence object is allocated memory but not properly released, leading to a gradual increase in memory usage. This leak occurs when the first reference of the DMA fence, initialized for management, is not released before the object is passed to the USB request context. Although the DMA reservation mechanism manages a second reference, the lack of a proper release for the first reference causes memory to be consumed without being freed. The vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed in the Linux kernel by modifying the DMA fence management. The patch transfers ownership of the fence to the DMA reservation object, ensuring that the fence is properly discarded after being signaled. Users can apply this patch to their Linux kernel source to fix the vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0cae3d6109427c455bad0a18dfb3e2a91657e38a | kernel.org | Patch |
| https://git.kernel.org/stable/c/b7475b2dce5e121e687280ba5732ccefe77ffd2f | kernel.org | Patch |
| https://git.kernel.org/stable/c/baa6b6068a3f2bf2ed525a1cb37975905dadc658 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e086c16962a1b0142e2675610e9c06fcfcd4c3a8 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-401 | Missing Release of Memory after Effective Lifetime | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.9, < 6.12.96 >= 6.13, < 6.18.39 >= 6.19, < 7.1.4 7.2 rc1 7.2 rc2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 4, 2026 | Initial Analysis | [email protected] |
| Aug 17, 2026 | CVE Modified | kernel.org |
| Jul 25, 2026 | New CVE Received | kernel.org |