Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98691 Overview
CVE-2026-98691 is a Linux kernel vulnerability in the Thunderbolt subsystem. The flaw involves improper teardown of inactive DisplayPort (DP) tunnels when the Thunderbolt domain is stopped. The tb_stop() function only tears down Direct Memory Access (DMA) tunnels, leaving DP tunnels still waiting for dprx_work to complete. The deferred work remains queued even after routers are removed and the control channel is stopped, causing the callback to execute against a torn-down domain. This produces a reference leak that blocks unbind completion until the DPRX timeout elapses.
Critical Impact
The flaw causes a Thunderbolt domain unbind operation to stall until the DPRX timeout expires, delaying device removal and keeping stale references to a torn-down domain.
Affected Products
- Linux kernel (Thunderbolt subsystem)
- Systems using Thunderbolt-connected DisplayPort devices
- Kernel versions prior to the fix commits referenced in the stable tree
Discovery Timeline
- 2026-10-18 - CVE-2026-98691 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-98691
Vulnerability Analysis
The vulnerability resides in the Linux kernel Thunderbolt driver. When the Thunderbolt domain is stopped, tb_stop() only tears down active DMA tunnels. DP tunnels still waiting for the dprx_work deferred work item to complete remain queued. These items are not canceled during domain teardown.
Because dprx_work requeues itself until the DPRX timeout fires, the flush_workqueue() call in tb_domain_remove() does not wait for its final run. The callback eventually executes against a domain that has already been torn down. A reference to that domain is retained by the pending work. The completion that waits for the domain to disappear during unbind blocks until the DPRX timeout expires.
This is a kernel driver resource-management defect in the Thunderbolt subsystem. It affects system responsiveness during device removal rather than enabling remote code execution.
Root Cause
The root cause is incomplete tunnel cleanup in tb_stop(). The function tears down DMA tunnels but ignores DP tunnels that have not yet activated. Pending dprx_work items hold references to the domain and keep requeuing themselves, preventing timely cleanup by flush_workqueue().
Attack Vector
This issue is a local kernel reliability defect triggered during normal device teardown or driver unbind operations. No remote attack vector is documented. A local user with physical access or control over Thunderbolt device connect and disconnect events may be able to repeatedly trigger the stall. Exploitability for privilege escalation is not indicated by the available data.
The fix tears down DP tunnels that are not yet active during domain stop, which also cancels the pending dprx_work. Tunnels for displays already active continue to function. See the upstream commits for implementation details.
Detection Methods for CVE-2026-98691
Indicators of Compromise
- Prolonged hangs or delays during Thunderbolt device unbind or system shutdown operations.
- Kernel log messages referencing stalled dprx_work or Thunderbolt domain removal timeouts.
- Zombie Thunderbolt domain references persisting after device disconnection.
Detection Strategies
- Monitor kernel ring buffer (dmesg) for Thunderbolt subsystem warnings during domain teardown.
- Inventory running kernel versions across endpoints and compare against the patched versions referenced in the kernel.org stable commits.
- Audit workqueue state via /proc and sysfs to identify long-lived dprx_work items on affected hosts.
Monitoring Recommendations
- Track Thunderbolt device connect and disconnect events in system logs for abnormal patterns.
- Alert on systems reporting delayed unbind completions longer than the expected DPRX timeout window.
- Centralize kernel telemetry from Linux endpoints into a security data lake for correlation.
How to Mitigate CVE-2026-98691
Immediate Actions Required
- Identify Linux systems running kernel versions that include the Thunderbolt DP tunnel code path without the fix.
- Apply the stable kernel updates containing the referenced commits as soon as vendor patches are available.
- Prioritize patching on laptops and workstations that use Thunderbolt-attached displays or docking stations.
Patch Information
The fix tears down inactive DP tunnels alongside DMA tunnels when the Thunderbolt domain is stopped. This also cancels pending dprx_work items, preventing the callback from running against a removed domain. Patches are available in the Linux kernel stable tree via commits 0b457c6, 34a6e27, and cbd2abb.
Workarounds
- Disconnect Thunderbolt DisplayPort devices before initiating driver unbind or system shutdown on unpatched hosts.
- Disable the Thunderbolt controller via firmware settings on systems that do not require Thunderbolt functionality.
- Blacklist the thunderbolt kernel module where the subsystem is not needed to eliminate exposure to the defect.
# Verify installed kernel version against patched references
uname -r
# Blacklist the thunderbolt module on systems that do not require it
echo "blacklist thunderbolt" | sudo tee /etc/modprobe.d/blacklist-thunderbolt.conf
sudo update-initramfs -u
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

