thunderbolt: Mark XDomain as unplugged when router is removed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 16603153666d22df544ae9f9b3764fd18da28eeb · < e2006140ad2e01a02ed0aff49cc2ae3ceeb11f8d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Mark XDomain as unplugged when router is removed
I noticed that when we do discrete host router NVM upgrade and it gets hot-removed from the PCIe side as a result of NVM firmware authentication, if there is another host connected with enabled paths we hang in tearing them down. This is due to fact that the Thunderbolt networking driver also tries to cleanup the paths and ends up blocking in tb_disconnect_xdomain_paths() waiting for the domain lock.
However, at this point we already cleaned the paths in tb_stop() so there is really no need for tb_disconnect_xdomain_paths() to do that anymore. Furthermore it already checks if the XDomain is unplugged and bails out early so take advantage of that and mark the XDomain as unplugged when we remove the parent router.
From the CVE record · Linux
The Linux kernel can hang while tearing down Thunderbolt networking paths when a discrete host router is hot-removed during an NVM firmware upgrade and another host is connected with enabled paths. The description does not identify an attacker, an authentication requirement, or a separate user-interaction requirement.
Engineers running Linux systems with Thunderbolt networking should check their kernel; affected versions are not specified.