usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel's USB gadget FunctionFS code, two error paths can call dma_fence_put() on a fence before it has been initialized, causing undefined behavior. The input does not specify how an attacker could trigger these paths or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with USB gadget FunctionFS should check their versions; affected versions are not specified.