CVE-2026-74585

thunderbolt: Bound the DROM dual link port number before indexing sw->ports

N/A
Published: August 22, 2026 at 03:31 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Bound the DROM dual link port number before indexing sw->ports tb_drom_parse_entry_port() validates the device-supplied header->index against sw->config.max_port_number before indexing sw->ports[], but the sibling field entry->dual_link_port_nr -- a 6-bit value also read from the DROM -- indexes the same array with no such check. A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced. Reject a port entry whose dual_link_port_nr exceeds max_port_number, the same bound already applied to header->index.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6
Vendor states this is fixed in 3d3c212b70633332ab71672aa2bc6af257d2ec83 (fixed)
Vendor states this is fixed in 40d2ffb74094cf36edbe05855566a4c58b6ce808 (fixed)
Vendor states this is fixed in 50f0c8dd8c3390f851cfb97ca13116f9ee6469d1 (fixed)
Vendor states this is fixed in 6c892ed9f4129ae40ef0f92e1bb31aa0b0ddc72c (fixed)
Vendor states this is fixed in b98e1e28bd95b0fa33164eec1e763d26c7058b39 (fixed)
Vendor states this is fixed in d6764992f17b23d91ff93ce905ab53c2aa7191f0 (fixed)
Vendor states this is fixed in f28066057134aa9294caa597b670daf505ad9dce (fixed)
Vendor states this is fixed in f32c3a9a77cfb50934a60b05d5407649af062535 (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card