Look up another CVE · open CVE-2026-80736 in the interactive tracker
CVE-2026-80736
thunderbolt: Fix bandwidth group reservation indexing
Published 2026-09-03 (2 months ago) by the Linux kernel CNA. Subsystem drivers/thunderbolt. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80736 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 | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.105-1 | Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Valid bandwidth group IDs range from 1 through MAX_GROUPS, while Group ID 0 is reserved. tb_consumed_dp_bandwidth() uses the Group ID directly to index its local group_reserved[] array. The array currently has MAX_GROUPS entries, so its valid indices are 0 through MAX_GROUPS - 1. Group ID MAX_GROUPS therefore accesses one element past the end, and the final group's reserved bandwidth is not included when the array is summed. Give group_reserved[] MAX_GROUPS + 1 entries so direct Group ID indexing covers the reserved ID 0 and valid IDs 1 through MAX_GROUPS.
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/tb.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-03 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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 |
|---|---|---|
| 6.9 | 6.12.104 | 0bfb67ba366c |
| 6.9 | 6.18.45 | 9977321835c7 |
| 6.9 | 7.1.9 | 0a8c9ed4f166 |
| 6.9 | 7.2 | d2ee4d47aacb |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | 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:LAttack vector, local
- The flaw is reached through the local Thunderbolt connection manager control channel (TB_CFG_ERROR_DP_BW notifications into tb_handle_dp_bandwidth_request/tb_alloc_dp_bandwidth), not over IP; on systems with authorized TB docks/workstations, DP bandwidth recalculation can be driven without new network access.
- AC:LAttack complexity, low
- After an authorized topology uses bandwidth group 7 with reserved DP bandwidth, the out-of-bounds write at group_reserved[7] is deterministic whenever tb_consumed_dp_bandwidth() runs; an attacker can induce the needed bandwidth reductions/mode changes rather than depending on uncontrollable timing.
- PR:LPrivileges required, low
- The vulnerable path performs no credential checks; once Thunderbolt devices are authorized (common with security level none or boot ACL), an unprivileged local user can trigger DP bandwidth allocation events via display/mode changes that cause DPTX bandwidth notifications.
- UI:NUser interaction, none
- No victim interaction is required beyond normal authorized Thunderbolt/DisplayPort operation; a local attacker can directly cause the bandwidth-change notifications that reach tb_consumed_dp_bandwidth() without convincing another user to perform a separate action.
- S:UScope, unchanged
- Impact is kernel stack corruption during Thunderbolt bandwidth accounting in the host kernel; it does not cross a VM/host, IOMMU/DMA, or sandbox security boundary and stays within the same kernel security authority.
- C:HConfidentiality impact, high
- Indexing group_reserved[] with group ID 7 writes one 32-bit word past a seven-element stack array, corrupting adjacent stack data with attacker-influenced reserved-bandwidth values and enabling kernel memory disclosure primitives.
- I:HIntegrity impact, high
- This is a kernel stack out-of-bounds write with partially attacker-controlled values (reserved Mb/s), which can corrupt pointers/control data on the stack and be leveraged for arbitrary kernel memory modification or privilege escalation.
- A:HAvailability impact, high
- Corrupting kernel stack variables in tb_consumed_dp_bandwidth() can cause immediate kernel oops/panic or hang during bandwidth accounting, and unstable stack corruption commonly produces severe system unavailability.