From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80989: net: thunderbolt: Mark the connection down when bringing it up fails
Date: Fri, 11 Sep 2026 21:41:35 +0200 [thread overview]
Message-ID: <2026091148-CVE-2026-80989-3c4c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-09-11 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091148-CVE-2026-80989-3c4c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.