GHSA-HVV7-VW9M-6V98
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-18 18:32In the Linux kernel, the following vulnerability has been resolved:
usb: typec: ucsi: glink: fix use-after-free of ucsi on remove
The pmic_glink client is released by the devres cleanup, which runs after pmic_glink_ucsi_remove() has returned, so its notification callbacks can queue work until then. Work that runs after ucsi_unregister() has been called touches freed state: it dereferences the connector array that ucsi_unregister() freed, or registers and unregisters the instance a second time.
Disable both work items with disable_work_sync() before unregistering, and unregister only if the instance is still registered.
This issue was found by an in-house static analysis tool.
{
"affected": [],
"aliases": [
"CVE-2026-98758"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:29Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: glink: fix use-after-free of ucsi on remove\n\nThe pmic_glink client is released by the devres cleanup, which runs\nafter pmic_glink_ucsi_remove() has returned, so its notification\ncallbacks can queue work until then. Work that runs after\nucsi_unregister() has been called touches freed state: it dereferences\nthe connector array that ucsi_unregister() freed, or registers and\nunregisters the instance a second time.\n\nDisable both work items with disable_work_sync() before unregistering,\nand unregister only if the instance is still registered.\n\nThis issue was found by an in-house static analysis tool.",
"id": "GHSA-hvv7-vw9m-6v98",
"modified": "2026-10-18T18:32:02Z",
"published": "2026-10-18T18:32:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98758"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/41934f92e7a54d4080ac0b17aacc83224946785c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/432b58cd959e594909a581b4974396cdbc9d4ca1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/63b269ec537dc0fd26d0bd64872c26860d108c9d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee8577de01c6b6c7dd1d76b52242c54d37a989f4"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.