thunderbolt: Make the DP tunnel activation callback mandatory
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 12f5d8b85a66a0ac08d082517d92ce136f8c0d42, Kernel 39a2c4e5e606cf49b83595971b449b3fb80743c6, Kernel 47d60ea801fc333a10c576691eca2e7840b02d3d and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <12f5d8b85a66a0ac08d082517d92ce136f8c0d42, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <39a2c4e5e606cf49b83595971b449b3fb80743c6, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <47d60ea801fc333a10c576691eca2e7840b02d3d | 12f5d8b85a66a0ac08d082517d92ce136f8c0d42, 39a2c4e5e606cf49b83595971b449b3fb80743c6, 47d60ea801fc333a10c576691eca2e7840b02d3d |
| linux-kernel: Kernel | >=6.14.0 <6.18.61, >=6.19.0 <7.2.10 | 6.18.61, 7.2.10 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket