thunderbolt: Fix domain reference leak when DPRX read is canceled
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From d6d458d42e1e1544a18f37f1d5c840e00d5261b9 · fixed in 2f5893172fc6153f5f1ef34014ddbfcbf1f47f29; From d6d458d42e1e1544a18f37f1d5c840e00d5261b9 · fixed in 7739b02129b2248f9a8054cfda924fa253f66a88; From d6d458d42e1e1544a18f37f1d5c840e00d5261b9 · fixed in 1fd1f67c94d30889377bba774f032ec15e8b9299
- Linux Linux
6.14
- KernelLinux
From 6.14.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10