From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795100761; b=v9z2QOCfgKimWpHZNaDj6qKlXLq+1Hp9hL/8tcxhTEec0Q1wVI0Qtt3MLDwFdcIdxqA6 razDi1WSvM3KlBs8dtyZRw6/txvYnNce+Zh+26m7xGV/86URntxgXUKs1WzZxjl1fl0UA 9V71e43Wu8ak9vS6ouuW//lr6zicvjvs9mUK8/xXGcRzJq8CKSf1/Ndn2ohvpC/ZqCWca rCDOsbMQx8q2ICnyD62A6XWNPRDYFXpOaDBcoNJbnB7Fal74sMN0QF48pDGiXDmIViWin ejnnh6tfSJZmodbE8NrBa9RpmzxxiJUj801p9yIxGij/DshhsZjmxzOwnSM91scvx7Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100761; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=iBYZZOolfsIi1JLBF8+ZBn/Bkt3s/EJg8/q/zXMnRDs=; b=AzH2/y5MZz//9qGIpmfq9VZHRYQxLnTX6jD0m14gsh3upoq77HCZyorCQSw+TadVp2lA /BvfJCI3nEJHkDwYTTgO176DTUDB/Go2KssznULPkZ+kfTjjFYGiQ9CONh3gka7orIWl5 sksPKiEsQAaM9Hy2TdWNQ8n2f8Oj6uwdthAoSie7+9+2nCYjykOEq5/JdwwDGDOTY95eA SD3CKQfv2+jKjXR+8y+BzodavNUKawEOeg6c5pJ7Oono5dQmttT3prHMOjAbNFMzFp4k9 8p8v+b4eCgNf1+vSyL96vXiqquUYUFs6/3rlPdOonq3syEbwWsJg+a6iZXVBeIgaRwA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=JmKSNxYg; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD1F3606A326 for ; Thu, 19 Nov 2026 15:06:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=JmKSNxYg Received: by smtp.kernel.org (Postfix) with ESMTPSA id 419A51F000C4; Thu, 19 Nov 2026 15:05:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100761; bh=iBYZZOolfsIi1JLBF8+ZBn/Bkt3s/EJg8/q/zXMnRDs=; h=From:To:Cc:Subject:Date:Reply-To; b=JmKSNxYgr+Swibw0hPO9SiVQ6RAAH5aU/TxqFaZZSuNf0Tx8HRFmjMOk7c8+Zw018 0BSwfHnBNkbXt1tYYBgLw9YXj+CmfWaTpA1f66EoD9RXR2aXoqhalrzdEwSmE/e2AN gQOVfMv5stZGNyS9sMWJdO9Vj4eaxhc6f4LXGXEc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99547: thunderbolt: Do not RPM complete unrelated subtrees on unplug Date: Thu, 19 Nov 2026 15:27:25 +0100 Message-ID: <2026111925-CVE-2026-99547-5934@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4754; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=hXO1TRQlcFZ3f4zPVEDs7+yIRAyZzM8mowuUxM0Q/YA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2WZWiF7MbQg65yleevehQnPOgX9MXqcXt7Rbf2Ixm pb1PXhNRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAExEbibDHM6H0+0cA5IOaHj4 ZGi8dc/PPvjpBsNc0VVLBApW7pR90js1ZHvY1/rMGQ80AQ== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== 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. The Linux kernel CVE team has assigned CVE-2026-99547 to this issue. Affected and fixed versions =========================== Issue introduced in 5.2 with commit 4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 and fixed in 6.12.117 with commit a7f354751b05ead5538176deadb9bc5b1fda0a3c Issue introduced in 5.2 with commit 4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 and fixed in 6.18.61 with commit 85a8777c7ec5e17b999b4c9eb0c8cbf4ab936998 Issue introduced in 5.2 with commit 4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 and fixed in 7.3.2 with commit e45356d83adce72fd99f57763eb3456c7c560857 Issue introduced in 5.2 with commit 4f7c2e0d8765a0266b920c66ffc495fde44c1ec8 and fixed in 7.4-rc1 with commit 96a8479804e3f7af43e639e9df39f562f1a75fd5 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-99547 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/thunderbolt/icm.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/a7f354751b05ead5538176deadb9bc5b1fda0a3c https://git.kernel.org/stable/c/85a8777c7ec5e17b999b4c9eb0c8cbf4ab936998 https://git.kernel.org/stable/c/e45356d83adce72fd99f57763eb3456c7c560857 https://git.kernel.org/stable/c/96a8479804e3f7af43e639e9df39f562f1a75fd5