Answer in brief
CVE-2026-80989 records a Unknown severity vulnerability in net: thunderbolt: Mark the connection down when bringing it up fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e <ed1d6e3d735e7b03f43a02f4306c89eb7663da14 || >=e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e <f01e6a35c440b62f060e21f36b385e574a7f308c || >=e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e <d6c0af293129345a17dc31c9b4179dc7f3d6af7a || >=e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e <3c8b26ebf525ba5960510f48c6e9936a79ebe76f | ed1d6e3d735e7b03f43a02f4306c89eb7663da14, f01e6a35c440b62f060e21f36b385e574a7f308c, d6c0af293129345a17dc31c9b4179dc7f3d6af7a, 3c8b26ebf525ba5960510f48c6e9936a79ebe76f |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.