Look up another CVE · open CVE-2026-97509 in the interactive tracker
CVE-2026-97509
thunderbolt: Keep XDomain reference during the lifetime of a service
Published 2026-09-24 (24 days ago) by the Linux kernel CNA. Subsystem drivers/thunderbolt. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-97509 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 | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
This is needed because we release the service ID in tb_service_release() and the ID array is owned by the parent XDomain.
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/xdomain.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, bookworm · linux-6.12?
- ?
- 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-09-24 (24 days ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.24%, higher than 13.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 |
|---|---|---|
| 4.15 | 5.10.266 | a4567e5380e4 |
| 4.15 | 5.15.217 | daeaa6c7211d |
| 4.15 | 6.1.189 | cca72fe513f3 |
| 4.15 | 6.6.158 | 57359bb31526 |
| 4.15 | 6.12.111 | 8ab12d015884 |
| 4.15 | 6.18.53 | ea60ae6233ca |
| 4.15 | 7.2 | 8b4060998637 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- enumerate_services() runs from tb_xdomain_get_properties() after the peer's PROPERTIES_RESPONSE (tb_xdp_properties_request on the Thunderbolt/USB4 control channel) so tb_service children exist; the same peer's link-down hits tb_handle_hotplug() then tb_xdomain_unregister(). That is the TB fabric, not a routable IP protocol.
- AC:LAttack complexity, low
- The peer controls both sides: property-block directories make enumerate_services() device_register() services without get_device(&xd->dev), then dropping the link runs tb_xdomain_unregister() → unregister_service() → device_del() put_device(parent) before tb_service_release() uses xd->service_ids. Advertise/unplug can be retried; no attacker-independent fault is required.
- PR:NPrivileges required, none
- tb_domain_event_cb delivers TB_CFG_PKG_XDOMAIN_REQ/RESP to tb_xdomain_handle_request whenever tb_is_xdomain_enabled() (xdomain module_param defaults true, plus ACPI OSC). UUID/property handshake and enumerate_services() run with no device authorization or local credentials on the victim.
- UI:NUser interaction, none
- tb_xdomain_add() starts the handshake by itself; enumerate_services() and later tb_xdomain_unregister() (tb_domain_unregister_unplugged_xdomains after unplug) run from the connection-manager hotplug path with no victim mount, sysfs write, or authorization dialog.
- S:UScope, unchanged
- tb_service_release() ida_free()s the already-freed tb_xdomain.service_ids IDA in the host kernel; that does not cross a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- After tb_xdomain_release() kfree()s the XDomain, tb_service_release() calls tb_service_parent() (reads svc->dev.parent->type) and ida_free(&xd->service_ids). That slab UAF of struct tb_xdomain can be reclaimed for an arbitrary kernel read.
- I:HIntegrity impact, high
- ida_free() writes the IDA/XArray embedded in the already-freed tb_xdomain; a sprayed replacement object is a kernel write and control-flow hijack primitive, as in other parent-IDA lifetime UAFs.
- A:HAvailability impact, high
- tb_service_release() on a kfree'd tb_xdomain (parent type-check or ida_free of destroyed service_ids) oopses or panics the host; the peer can repeat advertise-and-unplug cycles to take Thunderbolt down.