Answer in brief
CVE-2026-98689 records a Unknown severity vulnerability in thunderbolt: Don't access a DP tunnel after its DPRX read was 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 <405a969c0b3356639116db89ab367be1d64b77c0 || >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <2c2fd6a7fd5e1218db7e17336fc1a0393b6949e6 || >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <419fa32fa5bc2d7fb9d0d15d5630b1c1090808b3 | 405a969c0b3356639116db89ab367be1d64b77c0, 2c2fd6a7fd5e1218db7e17336fc1a0393b6949e6, 419fa32fa5bc2d7fb9d0d15d5630b1c1090808b3 |
| 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: Don't access a DP tunnel after its DPRX read was canceled tb_dp_dprx_work() checks ->dprx_canceled before it takes tb->lock so it misses a tb_dp_dprx_stop() that could not cancel the already running work. It then polls the DPRX capabilities and runs the callback for a tunnel that has already been torn down while the domain is suspending or going away. This can be hit by cancelling the DPRX read from outside the ordered tb->wq: During suspend tb_disconnect_and_release_dp() does just this and with a later patch tb_stop() will do it as well. The latter in combination with the Apple NHI where the DPRX read never completed is how I hit this. Check the flag with tb->lock held instead and check it again in tb_dp_tunnel_active() because the callback runs after the lock has been dropped again. Also clear the flag in tb_dp_dprx_start() so that it only ever describes the work that is currently in flight.
Quoted source text, attributed separately from HOL analysis.