First published: Fri Sep 13 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | <5.10.225 | |
Linux Linux kernel | >=5.11<5.15.166 | |
Linux Linux kernel | >=5.16<6.1.107 | |
Linux Linux kernel | >=6.2<6.6.48 | |
Linux Linux kernel | >=6.7<6.10.7 | |
Linux Linux kernel | =6.11-rc1 | |
Linux Linux kernel | =6.11-rc2 | |
Linux Linux kernel | =6.11-rc3 | |
debian/linux | <=5.10.223-1 | 5.10.226-1 6.1.115-1 6.1.112-1 6.11.7-1 6.11.9-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.