CVE-2026-80989

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.