CVEvulnerability
CVE-2026-64328
5.5 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-07-25
- Last modified
- 2026-09-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-401
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.
Affected configurations
• linux linux kernel (>= 6.9 < 6.12.96)
• linux linux kernel (>= 6.13 < 6.18.39)
• linux linux kernel (>= 6.19 < 7.1.4)
• linux linux kernel 7.2
Related
Weakness · CWE (1)
- CWE-401 Missing Release of Memory after Effective Lifetime weakness
References
- https://git.kernel.org/stable/c/0cae3d6109427c455bad0a18dfb3e2a91657e38a Patch
- https://git.kernel.org/stable/c/b7475b2dce5e121e687280ba5732ccefe77ffd2f Patch
- https://git.kernel.org/stable/c/baa6b6068a3f2bf2ed525a1cb37975905dadc658 Patch
- https://git.kernel.org/stable/c/e086c16962a1b0142e2675610e9c06fcfcd4c3a8 Patch