thunderbolt: Fix domain reference leak when DPRX read is canceled
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1fd1f67c94d30889377bba774f032ec15e8b9299, Kernel 2f5893172fc6153f5f1ef34014ddbfcbf1f47f29 and Kernel 7739b02129b2248f9a8054cfda924fa253f66a88.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.14, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <1fd1f67c94d30889377bba774f032ec15e8b9299, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <2f5893172fc6153f5f1ef34014ddbfcbf1f47f29, >=d6d458d42e1e1544a18f37f1d5c840e00d5261b9 <7739b02129b2248f9a8054cfda924fa253f66a88 | 1fd1f67c94d30889377bba774f032ec15e8b9299, 2f5893172fc6153f5f1ef34014ddbfcbf1f47f29, 7739b02129b2248f9a8054cfda924fa253f66a88 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket