All reports
Medium

kernel: usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-93121

Probability of exploitation in the next 30 days: 0.16%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in the Linux kernel's USB gadget function filesystem (f_fs) component. Specifically, an issue in the ffs_dmabuf_transfer() function's error handling can lead to undefined behavior. This occurs when a fence object is prematurely deallocated without proper initialization, potentially causing system instability or other unpredictable outcomes.