Answer in brief
CVE-2026-98690 records a Unknown severity vulnerability in thunderbolt: Fix domain reference leak when DPRX read is canceled. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <2f5893172fc6153f5f1ef34014ddbfcbf1f47f29 || >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <7739b02129b2248f9a8054cfda924fa253f66a88 || >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <1fd1f67c94d30889377bba774f032ec15e8b9299 | 2f5893172fc6153f5f1ef34014ddbfcbf1f47f29, 7739b02129b2248f9a8054cfda924fa253f66a88, 1fd1f67c94d30889377bba774f032ec15e8b9299 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.