GHSA-7H52-F32W-M42C
Vulnerability from github – Published: 2026-09-25 15:31 – Updated: 2026-09-25 15:31In the Linux kernel, the following vulnerability has been resolved:
usb: typec: ucsi: unregister debugfs entries on teardown
ucsi_register() creates per-instance debugfs entries, but ucsi_unregister() keeps them around until ucsi_destroy().
Drivers like ucsi_glink that unregister/register the same UCSI instance across remoteproc restart then try to create an already existing debugfs directory and log:
debugfs: 'pmic_glink.ucsi.0' already exists in 'ucsi'
Unregister debugfs entries as part of ucsi_unregister(), and clear ucsi->debugfs after freeing it so repeated unregister paths remain safe.
{
"affected": [],
"aliases": [
"CVE-2026-100079"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T14:17:15Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: unregister debugfs entries on teardown\n\nucsi_register() creates per-instance debugfs entries, but\nucsi_unregister() keeps them around until ucsi_destroy().\n\nDrivers like ucsi_glink that unregister/register the same UCSI\ninstance across remoteproc restart then try to create an already\nexisting debugfs directory and log:\n\n debugfs: \u0027pmic_glink.ucsi.0\u0027 already exists in \u0027ucsi\u0027\n\nUnregister debugfs entries as part of ucsi_unregister(), and\nclear ucsi-\u003edebugfs after freeing it so repeated unregister\npaths remain safe.",
"id": "GHSA-7h52-f32w-m42c",
"modified": "2026-09-25T15:31:46Z",
"published": "2026-09-25T15:31:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-100079"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1f44d001620fd3caa30619a9bc73e9d15555408b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/62efee351566321ad72a4abaf6eb7d972590585d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7177c215e69658adbd2f2fc5b72e14be9208d2ba"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eed73a65ab609b79d53de88cccc34b36dfe753c4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb7393519908befdc094be4ea913f582adbf2f7c"
}
],
"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.