thunderbolt: Tear down inactive DP tunnels when the domain is stopped
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.567.2.107.3In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Tear down inactive DP tunnels when the domain is stopped
tb_stop() only tears down DMA tunnels so a DP tunnel that is still waiting for dprx_work to complete keeps that work queued while the routers are removed and the control channel is stopped. The work only stops once the DPRX timeout has passed and because it requeues itself until then the flush_workqueue() in tb_domain_remove() won't wait for its final run. The callback then runs against a domain that is already torn down. A reference to that domain is kept so the completion waiting for that domain to disappear in unbind will block until the timeout is eventually reached.
Tear down DP tunnels that are not active yet as well which also cancels that work. Tunnels for displays that are already alive are untouched and keep working.
From the CVE record · Linux
In the Linux kernel’s Thunderbolt code, stopping a domain can leave work queued for an inactive DisplayPort tunnel. That work can run after the domain is torn down and delay unbinding until the DPRX timeout. The input does not describe an attacker path, authentication requirement, or user interaction.
Operators running Linux kernels with Thunderbolt DisplayPort tunnel support should check their versions; no affected versions are specified.