CVE-2026-98692
thunderbolt: Make the DP tunnel activation callback mandatory
What happened?
In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Make the DP tunnel activation callback mandatory
tb_tunnel_alloc_dp() takes an optional callback which is run from dprx_work once the DPRX capabilities read has completed. Without that callback tb_dp_dprx_start() reads the capabilities synchronously and never queues the work. It however always takes a tunnel reference which is only dropped by dprx_work itself or by tb_dp_dprx_stop() when cancel_delayed_work() actually canceled that work. That reference is thus leaked for every tunnel without a callback.
The only tunnels without one are those from tb_tunnel_discover_dp(), which are activated again when restoring from hibernation. Pass the callback to tb_tunnel_discover_dp() as well and drop the synchronous path such that the DPRX capabilities are always read from dprx_work. Hibernation restore then also no longer blocks for up to 12 seconds while waiting for that read to complete.
Also fix up the KUnit tests.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: d6d458d42e1e1544a18f37f1d5c840e00d5261b9 to < 39a2c4e5e606cf49b83595971b449b3fb80743c6; affected: d6d458d42e1e1544a18f37f1d5c840e00d5261b9 to < 47d60ea801fc333a10c576691eca2e7840b02d3d; affected: d6d458d42e1e1544a18f37f1d5c840e00d5261b9 to < 12f5d8b85a66a0ac08d082517d92ce136f8c0d42 | See vendor advisory |
| LinuxLinux | affected: 6.14; unaffected: 0 to < 6.14; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.10 to ≤ 7.2.*; unaffected: 7.3 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.