CVE-2026-99547

published 19 Nov 2026 · updated 21 Nov 2026

thunderbolt: Do not RPM complete unrelated subtrees on unplug

4.2MediumCVSS 4.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e45356d83adce72fd99f57763eb3456c7c560857, Kernel 85a8777c7ec5e17b999b4c9eb0c8cbf4ab936998, Kernel 96a8479804e3f7af43e639e9df39f562f1a75fd5 and 4 more.

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 0xffff_ffff_ffff_fff8 on unplug from one side of the laptop and went bug hunting. I became suspicious of the `bus_for_each_dev()` walk that I ultimately ended up changing. To confirm this issue, I did an eBPF trace of `bus_for_each_dev()`, `complete_rpm()`, and `complete()` while unplugging in a variety of situations and found that an unplug from domain 0 tries to `complete_rpm()` 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: ``` RESCAN_ENTER domain=0 COMPLETE rescan_domain=0 target=0-1 target_domain=0 route=0x1 parent=0-0 unplugged=1 COMPLETION done=0 head=HEAD next=HEAD prev=HEAD BUS_WALK domain=0 start=0-1 callback=complete_rpm CALLBACK_ENTER rescan_domain=0 dev=1-0 parent=domain1 is_switch=1 COMPLETE rescan_domain=0 target=1-0 target_domain=1 route=0x0 parent=domain1 unplugged=0 COMPLETION done=0 head=HEAD next=0 prev=0 complete+5 complete_rpm+43 bus_for_each_dev+133 icm_free_unplugged_children+250 icm_rescan_work+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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 <e45356d83adce72fd99f57763eb3456c7c560857, >=4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 <85a8777c7ec5e17b999b4c9eb0c8cbf4ab936998, >=4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 <96a8479804e3f7af43e639e9df39f562f1a75fd5, >=4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 <a7f354751b05ead5538176deadb9bc5b1fda0a3c, =5.2e45356d83adce72fd99f57763eb3456c7c560857, 85a8777c7ec5e17b999b4c9eb0c8cbf4ab936998, 96a8479804e3f7af43e639e9df39f562f1a75fd5, a7f354751b05ead5538176deadb9bc5b1fda0a3c
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.2.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99547 severity on Zeptric[![CVE-2026-99547](https://zeptric.io/badge/cve/CVE-2026-99547.svg)](https://zeptric.io/cve/CVE-2026-99547)