Look up another CVE · open CVE-2026-98690 in the interactive tracker
CVE-2026-98690
thunderbolt: Fix domain reference leak when DPRX read is canceled
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/thunderbolt. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-98690 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 ("thunderbolt: Wait for tb_domain_release() to complete when driver is removed") instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver. This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver. That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn't matter anymore if the callback ever runs.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/thunderbolt/tb.c
drivers/thunderbolt/tunnel.c
- What this is
- THUNDERBOLT DRIVERMAINTAINERS section matched on drivers/thunderbolt/ · linux-usb@vger.kernel.org · Maintained
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/thunderbolt
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.14 | 6.18.56 | 2f5893172fc6 |
| 6.14 | 7.2.10 | 7739b02129b2 |
| 6.14 | 7.3 | 1fd1f67c94d3 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98690, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.