From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7FB9E403E82 for ; Sat, 15 Aug 2026 12:33:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797233; cv=none; b=VlMKD9xzvrqjPLssqGTg1fPkZ3uCt/BSYbZSK8DJ96o7StHaKGDXdKwYwlN4JUIB2kYFL5WloUH30u3qa9x3+buIsz+lTftJnf4xg7a5ziNJQ1ln5cH9AeKhQwTe3DcW8DPCdhFCFJPClVIy852qAyM2gJE4BjMR0STxKKWUdDc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786797233; c=relaxed/simple; bh=lyBG9otwOefjOsH3ElJ34qCdG1YsNkI4AHDKXQtF21E=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=H5MZq+lf/A5ZLOGZEY2VKwS3i3pH8rSFOy/DebbVhRN15ChxP0MzwaggcTY3ZVoM2BQqiUlKTsFRjaS3aDso1jmuYunCsbsCsY7EhkSVmJmb59YadP9iKxOIvYuWPAo2BHa42cmXZbtOrO8Psb1QULlvOEkTw+IZ50pQmblIEuk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=YW87DBS9; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="YW87DBS9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D896B1F000E9; Sat, 15 Aug 2026 12:33:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786797232; bh=MJljpGVBRMw1ejEj2Uf0jvqTYpaAppn7B9FaBtYlFzU=; h=From:To:Cc:Subject:Date:Reply-To; b=YW87DBS9gHZuYqxQ5hel5LleUVXRv1o3nQcgiijGa0GnH3TkDgmqCzCy/Y60VTpId HPAFBZktCg9enUHBBrbR9w0kv40R/hbzuVIYayZMAcreqo/Q9RJdMC4Imm/Nmw5KeL vfdfq0QtlYdYqdPdthv/SU0YYlfCdnJjPOPODT8c= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74575: thunderbolt: Prevent XDomain delayed work use-after-free on disconnect Date: Sat, 15 Aug 2026 21:27:36 +0900 Message-ID: <2026081555-CVE-2026-74575-34d7@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3823; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=5oZaaX8SFXZYclO9NXHE+cXxgDWwZ9/Wlm18qDg537Q=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNUZf3GT852nb7bE2e1oGWic2Tle/X10mKLhKdrGiuc Kj3vXdVRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzE5wXDgrWxAnsP6ms2ejG9 TjXWkV2ipP45h2F+xpai8KbW5Leu1b3iRmXrvt7g/bIBAA== 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: Prevent XDomain delayed work use-after-free on disconnect tb_xdp_handle_request() runs on system_wq and queues xd->state_work via queue_delayed_work() in three request handlers: PROPERTIES_CHANGED_REQUEST, UUID_REQUEST (via start_handshake), and LINK_STATE_CHANGE_REQUEST. Similarly, update_xdomain() queues xd->properties_changed_work when local properties change. Concurrently, tb_xdomain_remove() calls stop_handshake() which does cancel_delayed_work_sync() on both delayed works. Later, tb_xdomain_unregister() calls device_unregister() which eventually frees the xdomain. Since commit 559c1e1e0134 ("thunderbolt: Run tb_xdp_handle_request() in system workqueue") moved the request handler off tb->wq, the handler and the remove path are no longer serialized. If queue_delayed_work() executes after cancel_delayed_work_sync() but before the xdomain is freed, the delayed work fires on a freed object. Add xd->removing that tb_xdomain_remove() sets under xd->lock before calling stop_handshake(). Each external queue site holds the same lock and checks removing before calling queue_delayed_work(). This provides the mutual exclusion needed: either the queue site acquires the lock first and queues work that the subsequent cancel will see, or the remove path acquires the lock first and the queue site observes removing == true and skips the queue. The Linux kernel CVE team has assigned CVE-2026-74575 to this issue. Affected and fixed versions =========================== Issue introduced in 5.2 with commit 559c1e1e013437bf190469efbcbd8bc803285853 and fixed in 6.6.151 with commit 91b40862a02000f490b63f1d315be3ee31e83871 Issue introduced in 5.2 with commit 559c1e1e013437bf190469efbcbd8bc803285853 and fixed in 6.12.103 with commit 33c0ee18cf8665c974b00f4e0ba769fbc07efe10 Issue introduced in 5.2 with commit 559c1e1e013437bf190469efbcbd8bc803285853 and fixed in 6.18.44 with commit 54a62153c765cd24239cde1f2633f2a2fd005368 Issue introduced in 5.2 with commit 559c1e1e013437bf190469efbcbd8bc803285853 and fixed in 7.1.8 with commit 2aa2cde2cc79a79d8ea4a15be9f4a67fc528ae91 Issue introduced in 5.2 with commit 559c1e1e013437bf190469efbcbd8bc803285853 and fixed in 7.2-rc1 with commit 2c5d2d3c3f70cde2565d7b279b544893a2035842 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-74575 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/xdomain.c include/linux/thunderbolt.h 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/91b40862a02000f490b63f1d315be3ee31e83871 https://git.kernel.org/stable/c/33c0ee18cf8665c974b00f4e0ba769fbc07efe10 https://git.kernel.org/stable/c/54a62153c765cd24239cde1f2633f2a2fd005368 https://git.kernel.org/stable/c/2aa2cde2cc79a79d8ea4a15be9f4a67fc528ae91 https://git.kernel.org/stable/c/2c5d2d3c3f70cde2565d7b279b544893a2035842