CVE-2026-74585: thunderbolt: Bound the DROM dual link port number before indexing sw->ports
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 3d3c212b70633332ab71672aa2bc6af257d2ec83, 40d2ffb74094cf36edbe05855566a4c58b6ce808, 50f0c8dd8c3390f851cfb97ca13116f9ee6469d1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3d3c212b70633332ab71672aa2bc6af257d2ec83, 40d2ffb74094cf36edbe05855566a4c58b6ce808, 50f0c8dd8c3390f851cfb97ca13116f9ee6469d1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 22, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.17affected
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before 6c892ed9f4129ae40ef0f92e1bb31aa0b0ddc72caffected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before 3d3c212b70633332ab71672aa2bc6af257d2ec83affected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before b98e1e28bd95b0fa33164eec1e763d26c7058b39affected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before 50f0c8dd8c3390f851cfb97ca13116f9ee6469d1affected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before f28066057134aa9294caa597b670daf505ad9dceaffected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before 40d2ffb74094cf36edbe05855566a4c58b6ce808affected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before f32c3a9a77cfb50934a60b05d5407649af062535affected · git
- cd22e73bdf5eff7e68a0f8bdfbce123ad43651f6 and later · before d6764992f17b23d91ff93ce905ab53c2aa7191f0affected · git
- before 3.17not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74583Aug 21, 2026 · net/sched: cls_route: fix fastmap use-after-free on filter31Monitor
- ← EarlierCVE-2026-74584Aug 22, 2026 · RDMA/bnxt_re: zero shared page before exposing to userspace28Monitor
- Later →CVE-2026-74586Aug 22, 2026 · sctp: clear new_transport when removing a peer39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3d3c212b70633332ab71672aa2bc6af257d2ec83 | Vendor (CNA) |
| Linux Linux | 40d2ffb74094cf36edbe05855566a4c58b6ce808 | Vendor (CNA) |
| Linux Linux | 50f0c8dd8c3390f851cfb97ca13116f9ee6469d1 | Vendor (CNA) |
| Linux Linux | 6c892ed9f4129ae40ef0f92e1bb31aa0b0ddc72c | Vendor (CNA) |
| Linux Linux | b98e1e28bd95b0fa33164eec1e763d26c7058b39 | Vendor (CNA) |
| Linux Linux | d6764992f17b23d91ff93ce905ab53c2aa7191f0 | Vendor (CNA) |
| Linux Linux | f28066057134aa9294caa597b670daf505ad9dce | Vendor (CNA) |
| Linux Linux | f32c3a9a77cfb50934a60b05d5407649af062535 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/40d2ffb74094cf36edbe05855566a4c58b6ce808
- git.kernel.org/stable/c/50f0c8dd8c3390f851cfb97ca13116f9ee6469d1
- git.kernel.org/stable/c/6c892ed9f4129ae40ef0f92e1bb31aa0b0ddc72c
- git.kernel.org/stable/c/b98e1e28bd95b0fa33164eec1e763d26c7058b39
- git.kernel.org/stable/c/d6764992f17b23d91ff93ce905ab53c2aa7191f0
- git.kernel.org/stable/c/f28066057134aa9294caa597b670daf505ad9dce
- git.kernel.org/stable/c/f32c3a9a77cfb50934a60b05d5407649af062535
Vendor advisories and official records. Exploit/PoC links are deliberately left out.