CVE-2026-98689

In the Linux kernel, the following vulnerability has been resolved:

thunderbolt: Don't access a DP tunnel after its DPRX read was canceled

tb dp dprx work() checks ->dprx canceled before it takes tb->lock so it misses a tb dp dprx stop() that could not cancel the already running work. It then polls the DPRX capabilities and runs the callback for a tunnel that has already been torn down while the domain is suspending or going away.

This can be hit by cancelling the DPRX read from outside the ordered tb->wq: During suspend tb disconnect and release dp() does just this and with a later patch tb stop() will do it as well. The latter in combination with the Apple NHI where the DPRX read never completed is how I hit this.

Check the flag with tb->lock held instead and check it again in tb dp tunnel active() because the callback runs after the lock has been dropped again.

Also clear the flag in tb dp dprx start() so that it only ever describes the work that is currently in flight.