GHSA-WQQH-3G59-38Q4
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Fix domain reference leak when DPRX read is canceled
tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 ("thunderbolt: Wait for tb_domain_release() to complete when driver is removed") instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver.
This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver.
That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn't matter anymore if the callback ever runs.
{
"affected": [],
"aliases": [
"CVE-2026-98690"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:22Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nthunderbolt: Fix domain reference leak when DPRX read is canceled\n\ntb_tunnel_one_dp() takes a domain reference which is only dropped once\ntb_dp_tunnel_active() has run on the work queue. If that work is\ncancelled that reference is leaked. Since\ncommit f5cc545f5969 (\"thunderbolt: Wait for tb_domain_release() to\ncomplete when driver is removed\") instead of just leaking memory this\nnow also blocks in the completion wait forever when unbinding the\ndriver.\n\nThis can be triggered whenever a DP tunnel is torn down before the DPRX\nread has completed, e.g. by unplugging within the timeout, and then\nunbinding the driver.\n\nThat reference only exists to keep the domain around while the DPRX work\nis scheduled so let the work itself own it: take it in tb_dp_dprx_start()\nand drop it in both places that end the work. Get/put are then paired\ninside the same file and it doesn\u0027t matter anymore if the callback ever\nruns.",
"id": "GHSA-wqqh-3g59-38q4",
"modified": "2026-10-18T18:31:59Z",
"published": "2026-10-18T18:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98690"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1fd1f67c94d30889377bba774f032ec15e8b9299"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2f5893172fc6153f5f1ef34014ddbfcbf1f47f29"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7739b02129b2248f9a8054cfda924fa253f66a88"
}
],
"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.