GHSA-VG86-RJRH-Q8JW
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-93121"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:06Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths\n\nThe error paths for endpoint-disabled (ESHUTDOWN) and request-allocation\nfailure (ENOMEM) in ffs_dmabuf_transfer() jump to err_fence_put which\ncalls dma_fence_put() on the fence. However, at that point the fence has\nonly been kmalloc\u0027d \u2014 dma_fence_init() has not been called yet, so the\nrefcount and the fence ops are uninitialized. Calling dma_fence_put() on\nsuch an object leads to undefined behavior.\n\nUse kfree() instead, since the fence is just a plain allocation at this\nstage, and rename the label to err_fence_free to reflect the actual\ncleanup action.",
"id": "GHSA-vg86-rjrh-q8jw",
"modified": "2026-09-17T18:32:11Z",
"published": "2026-09-17T18:32:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93121"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/58952c83dfe6ea3294a74734d2d1018c1120779a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5fd8baacc7dc477df9cac61b45491840247a9b1e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/621707dc67c9846fd876d7579ec951d92aa033f1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/be539138d9a187af3b884525a395db10797c64f1"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.