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 78A55582BA2 for ; Fri, 11 Sep 2026 19:49:47 +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=1789156190; cv=none; b=ElIW4pvwifAg6nUpYfOIO5SXy6UKph0sKbQxltWSTwfcb5Nr5H8BoOFHybqs8MLEW72SlV9i3Ll21OR3dCLXtJqF/etz98B5iaCYQknYXb5H8Im+3JP56voiw46vUpTAQVbl63At2VaOvO3RfMcRuCxXTXIqk0rINX/O3ZaiwHY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156190; c=relaxed/simple; bh=KgYYXHA6PYSZoqGookZ5C1BPXnhazuzQPRqmUG8Ppvc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=SL3nrjuE8Nw4GJ/QHuN5RdoQHK4ixIoFVrDWCfIofBUwX7AIEqW4tZfw7f/X2/zH5F7AhNtsnhgEDFJb5JuOfH5+G6U5AIe077Ak2A3Lx8sFW4gvHvWsc84cHSx40+J4ck706xoZKrP6ewfcrD6DrxroncChfiCoWE6SY0SNkWE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=DfdVAD+G; 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="DfdVAD+G" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5CEE31F00899; Fri, 11 Sep 2026 19:49:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156187; bh=Z53hWRCZ/l9/4RgJjTNIVLZogmEX3dbUsjpw6kSjZTs=; h=From:To:Cc:Subject:Date:Reply-To; b=DfdVAD+GEvnan1e7MLDBF/GraGNw1HI+rhS5zxmAdmnzue4Ll+eXoLHtsinvDn/yG JTLMjJ4izWb3ODroKG3yZhwZEqAacsofDkXAqzkWP5OjKz3nq3GOwv2d6pUAIUqcBp vrjKRGgvDFM+qeXn2uqDBLSodJixwkZTe4RJ9QIs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80989: net: thunderbolt: Mark the connection down when bringing it up fails Date: Fri, 11 Sep 2026 21:41:35 +0200 Message-ID: <2026091148-CVE-2026-80989-3c4c@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=3334; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=5tPrahdM4+tCvGKdTs3i/P6qsDAXHiQAUS9Hg92F8yY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIh1y/ttF21/K85sUUf9tQUiSCO+njFYv0YB9LG//P TGICl3ZEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABO5LsWw4MIrxnnegpmHp+hW Xi9JKHc8dN/2OMN8p8k5glZhT6cfbffhDb7e5SVrN6sSAA== 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: net: thunderbolt: Mark the connection down when bringing it up fails Every failure path in tbnet_connected_work() undoes its own work and returns without clearing login_sent, so the connection still looks established. The next tbnet_tear_down() therefore takes its main branch and repeats a teardown that already happened: it stops rings that are already stopped, which is a dev_WARN() and fatal under panic_on_warn, and it releases net->remote_transmit_path even on the HopID mismatch path, where this connection never owned that id, silently freeing one that someone else is still using. Clear login_sent on those paths. That is enough for tbnet_tear_down() to leave the unwound state alone, and login_received has to stay set: it records that the peer has logged in and carries the transmit path it gave us, which nothing on this side can make the peer send again. Two things change beyond keeping the teardown out of the way: the logout request in that block is no longer sent, and the peer's next login request now re-queues our login work rather than connected_work, giving the connection a fresh login instead of a retry on stale state. The Linux kernel CVE team has assigned CVE-2026-80989 to this issue. Affected and fixed versions =========================== Issue introduced in 4.15 with commit e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e and fixed in 6.12.109 with commit ed1d6e3d735e7b03f43a02f4306c89eb7663da14 Issue introduced in 4.15 with commit e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e and fixed in 6.18.50 with commit f01e6a35c440b62f060e21f36b385e574a7f308c Issue introduced in 4.15 with commit e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e and fixed in 7.2.4 with commit d6c0af293129345a17dc31c9b4179dc7f3d6af7a Issue introduced in 4.15 with commit e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e and fixed in 7.3-rc1 with commit 3c8b26ebf525ba5960510f48c6e9936a79ebe76f 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-80989 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/net/thunderbolt/main.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/ed1d6e3d735e7b03f43a02f4306c89eb7663da14 https://git.kernel.org/stable/c/f01e6a35c440b62f060e21f36b385e574a7f308c https://git.kernel.org/stable/c/d6c0af293129345a17dc31c9b4179dc7f3d6af7a https://git.kernel.org/stable/c/3c8b26ebf525ba5960510f48c6e9936a79ebe76f