CVE-2026-99547: thunderbolt: Do not RPM complete unrelated subtrees on unplug
In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Do not RPM complete unrelated subtrees on unplug
When a Thunderbolt device is unplugged, that switch and every switch subsequent to it on the bus device list is complete()d, not just its child devices. In the case of multiple domains, it may cause, eg, an attempt to complete() the uninitialized domain 1 root switch RPM completion on unplug of a switch from domain 0 (though ordering is not guaranteed numerically sorted).
I initially noticed this issue on a Dell XPS9720 when the system would seem to sporadically not wake after unplugging a Thunderbolt dock. I tried multiple kernel versions including v7.2.7 and v7.3-rc4 to see if that resolved the issue, but the issue persisted. Eventually I found that I could consistently generate a kernel Oops reporting a page fault at 0xfffffffffffffff8 on unplug from one side of the laptop and went bug hunting. I became suspicious of the busforeachdev() walk that I ultimately ended up changing. To confirm this issue, I did an eBPF trace of busforeachdev(), completerpm(), and complete() while unplugging in a variety of situations and found that an unplug from domain 0 tries to completerpm() domain 1's switch, whose RPM completion is not initialized and thus is holding a null wait-list pointer, triggering the page fault.
Here are the key sections of that eBPF trace. Note that HEAD denotes the completion's own wait-list HEAD:
RESCANENTER domain=0
COMPLETE rescandomain=0 target=0-1 targetdomain=0 route=0x1 parent=0-0 unplugged=1 COMPLETION done=0 head=HEAD next=HEAD prev=HEAD
BUSWALK domain=0 start=0-1 callback=completerpm CALLBACKENTER rescandomain=0 dev=1-0 parent=domain1 isswitch=1
COMPLETE rescandomain=0 target=1-0 targetdomain=1 route=0x0 parent=domain1 unplugged=0 COMPLETION done=0 head=HEAD next=0 prev=0
complete+5 completerpm+43 busforeachdev+133 icmfreeunpluggedchildren+250 icmrescanwork+42
This patch gates the complete() on an additional condition - that the Thunderbolt domain matches the domain of the device that was unplugged.
I only have a single system with multiple Thunderbolt domains - the Dell XPS9720. I am consistently able to reproduce the Oops on that system. Since running with this patch, I have not seen the Oops reoccur. I have also tested it on a Thinkpad X1-Gen12, and that system boots and runs well with it, but it only has a single Thunderbolt domain, so it does not exercise the multi-domain failure case.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1 - Compensating control
Gate complete() so it runs only when the Thunderbolt domain matches the domain of the unplugged device.