CVE-2026-98688 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Fix NULL dereference in tb_remove_work()
There is a slight race between tb_remove_work() and tb_domain_remove()
which leads to dereferencing a NULL tb->root_switch pointer inside
tb_free_unplugged_xdomains():
Thread A Thread B
tb_remove_work()
tb_domain_remove()
mutex_lock(&tb->lock)
tb_stop()
/* doesn't cancel a running callback */
cancel_delayed_work(&tcm->remove_work)
...
tb_switch_remove(tb->root_switch)
tb->root_switch = NULL
mutex_unlock(&tb->lock)
mutex_lock(&tb->lock)
...
/* without checking ->root_switch */
tb_free_unplugged_xdomains(tb->root_switch)
mutex_unlock(&tb->lock)
Commit a8937f35cf39 ("thunderbolt: Remove XDomain from the bus without
holding tb->lock") doesn't seem right to move tb_free_unplugged_xdomains()
out of the &tb->lock section and the check for tb->root_switch, in
particular. It states:
For this reason separate removing the XDomain from the topology data
structures (where we need the lock) from unregistering the device from
the bus (where remove callbacks of the drivers are being called).
tb_free_unplugged_xdomains() belongs to the former group of functions
requiring the lock. And it also calls tb_xdomain_remove() which should
only be called with &tb->lock held.
Found by Linux Verification Center (linuxtesting.org) with Svace static
analysis tool.
- EPSS
- 0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 7.2.10
- Linux Linux: fixed in 7.3
- Debian, Ubuntu: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-98688 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98688?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98688?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98688 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 5.10.266 before 5.11 |
| Linux | from 5.15.217 before 5.16 |
| Linux | 7.2 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.2 | 7.2.10 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.10-1 | DEBIAN-CVE-2026-98688 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 45 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | 24.04:LTS | linux-nvidia-tegra | 6.8.0-1039.40 | UBUNTU-CVE-2026-98688 USN-9091-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 23 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | 26.04:LTS | linux-oem-7.0 | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | Nvidia-BlueField:22.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | Pro:20.04:LTS | linux-aws-5.15, linux-gcp-5.15, linux-hwe-5.15 and 8 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | Pro:FIPS-updates:22.04:LTS | linux-fips, linux-aws-fips, linux-gcp-fips and 1 more | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime, linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-98688 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-98688 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat
Red Hat rates this Moderate.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98688.