Severity by source
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AV:A (Thunderbolt-adjacent only); AC:H because triggering the failure path requires specific mid-setup conditions; C:H downgraded to C:L since memory disclosure is speculative without POC.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
State machine corruption in the Linux kernel's Thunderbolt networking (tbnet) subsystem allows an adjacent attacker to trigger a double-teardown sequence that causes kernel panics or silently frees HopIDs still in use by other connections. The bug lies in tbnet_connected_work(): every failure path returns without clearing login_sent, so the connection appears established to tbnet_tear_down(), which then re-executes teardown on an already-unwound state - stopping rings already stopped (a dev_WARN, fatal under panic_on_warn) and potentially double-freeing net->remote_transmit_path on HopID mismatch paths. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Thunderbolt networking must be active: the thunderbolt_net kernel module must be loaded and a peer device must have already sent a valid login frame (login_received set). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.8 with AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H signals a high-severity adjacent network issue requiring no authentication. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to a patched kernel release: Linux 6.12.109, 6.18.50, 7.2.4, or 7.3-rc1 or later, per the EUVD-2026-76312 patch matrix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory Linux systems with Thunderbolt networking support enabled (verify via 'lsmod | grep tbnet' and device enumeration) and check your Linux distribution vendor for released kernel patches addressing CVE-2026-80989. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-76312
GHSA-fm3c-92pm-qq7p