thunderbolt: Fix bandwidth group reservation indexing
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thunderbolt: Fix bandwidth group reservation indexing
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.
From the CVE record · Linux
The Linux kernel’s Thunderbolt bandwidth calculation uses a group ID to index an array that is too small for the highest valid ID. Processing that ID accesses one element past the array and omits the final group’s reserved bandwidth from the total. The input does not specify an attack path, authentication requirement, or user interaction.
Engineers running Linux kernels with Thunderbolt support should check their versions; affected versions were not provided.