CVE-2024-46702: thunderbolt: Mark XDomain as unplugged when router is removed
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 tbdisconnectxdomainpaths() waiting for the domain lock.
However, at this point we already cleaned the paths in tbstop() so there is really no need for tbdisconnectxdomainpaths() 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46702?
CVE-2024-46702 has a medium severity rating due to its impact on the Linux kernel's Thunderbolt functionality.
How do I fix CVE-2024-46702?
To resolve CVE-2024-46702, upgrade to the recommended Linux kernel versions such as 5.10.226-1 or later.
Which systems are affected by CVE-2024-46702?
CVE-2024-46702 affects various versions of the Linux kernel, particularly versions before 5.10.226 and those in the ranges specified for 6.x series.
Is CVE-2024-46702 exploitable remotely?
CVE-2024-46702 may allow an attacker with local access to exploit the vulnerability, but it is not classified as a remote exploit.
What components are impacted by CVE-2024-46702 in the Linux kernel?
CVE-2024-46702 specifically impacts the Thunderbolt controller functionality within the Linux kernel.