Answer in brief
CVE-2026-64328 records a Unknown severity vulnerability in usb: gadget: f_fs: Fix DMA fence leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7b07a2a7ca02a20124b552be96c5a56910795488 <b7475b2dce5e121e687280ba5732ccefe77ffd2f || >=7b07a2a7ca02a20124b552be96c5a56910795488 <e086c16962a1b0142e2675610e9c06fcfcd4c3a8 || >=7b07a2a7ca02a20124b552be96c5a56910795488 <0cae3d6109427c455bad0a18dfb3e2a91657e38a || >=7b07a2a7ca02a20124b552be96c5a56910795488 <baa6b6068a3f2bf2ed525a1cb37975905dadc658 | b7475b2dce5e121e687280ba5732ccefe77ffd2f, e086c16962a1b0142e2675610e9c06fcfcd4c3a8, 0cae3d6109427c455bad0a18dfb3e2a91657e38a, baa6b6068a3f2bf2ed525a1cb37975905dadc658 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64328 records a Unknown severity vulnerability in usb: gadget: f_fs: Fix DMA fence leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7b07a2a7ca02a20124b552be96c5a56910795488 <b7475b2dce5e121e687280ba5732ccefe77ffd2f || >=7b07a2a7ca02a20124b552be96c5a56910795488 <e086c16962a1b0142e2675610e9c06fcfcd4c3a8 || >=7b07a2a7ca02a20124b552be96c5a56910795488 <0cae3d6109427c455bad0a18dfb3e2a91657e38a || >=7b07a2a7ca02a20124b552be96c5a56910795488 <baa6b6068a3f2bf2ed525a1cb37975905dadc658 | b7475b2dce5e121e687280ba5732ccefe77ffd2f, e086c16962a1b0142e2675610e9c06fcfcd4c3a8, 0cae3d6109427c455bad0a18dfb3e2a91657e38a, baa6b6068a3f2bf2ed525a1cb37975905dadc658 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.