Answer in brief
CVE-2026-93121 records a High severity (CVSS 7.0) vulnerability in usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths. 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.
CVSS is 7.0. 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 <be539138d9a187af3b884525a395db10797c64f1 || >=7b07a2a7ca02a20124b552be96c5a56910795488 <5fd8baacc7dc477df9cac61b45491840247a9b1e || >=7b07a2a7ca02a20124b552be96c5a56910795488 <58952c83dfe6ea3294a74734d2d1018c1120779a || >=7b07a2a7ca02a20124b552be96c5a56910795488 <621707dc67c9846fd876d7579ec951d92aa033f1 | be539138d9a187af3b884525a395db10797c64f1, 5fd8baacc7dc477df9cac61b45491840247a9b1e, 58952c83dfe6ea3294a74734d2d1018c1120779a, 621707dc67c9846fd876d7579ec951d92aa033f1 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths The error paths for endpoint-disabled (ESHUTDOWN) and request-allocation failure (ENOMEM) in ffs_dmabuf_transfer() jump to err_fence_put which calls dma_fence_put() on the fence. However, at that point the fence has only been kmalloc'd — dma_fence_init() has not been called yet, so the refcount and the fence ops are uninitialized. Calling dma_fence_put() on such an object leads to undefined behavior. Use kfree() instead, since the fence is just a plain allocation at this stage, and rename the label to err_fence_free to reflect the actual cleanup action.
Quoted source text, attributed separately from HOL analysis.