CVE-2024-46702

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> thunderbolt: Mark XDomain as unplugged when router is removed<br /> <br /> I noticed that when we do discrete host router NVM upgrade and it gets<br /> hot-removed from the PCIe side as a result of NVM firmware authentication,<br /> if there is another host connected with enabled paths we hang in tearing<br /> them down. This is due to fact that the Thunderbolt networking driver<br /> also tries to cleanup the paths and ends up blocking in<br /> tb_disconnect_xdomain_paths() waiting for the domain lock.<br /> <br /> However, at this point we already cleaned the paths in tb_stop() so<br /> there is really no need for tb_disconnect_xdomain_paths() to do that<br /> anymore. Furthermore it already checks if the XDomain is unplugged and<br /> bails out early so take advantage of that and mark the XDomain as<br /> unplugged when we remove the parent router.