Skip to content
Systems

CVE-2026-74575

8.8
High
EPSS 0.24%Patch availableAug 17, 2026

Use-after-free in Linux Thunderbolt xdomain allowing kernel crash or escalation.

common questions

Is CVE-2026-74575 being exploited?

Not confirmed. CVE-2026-74575 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-74575?

CVE-2026-74575 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74575?

Yes. A fix has been recorded for CVE-2026-74575. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74575 affect?

CVE-2026-74575 affects Linux kernel (Thunderbolt xdomain subsystem), Systems with Thunderbolt ports/controllers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74575?

Apply vendor/kernel update that fixes Thunderbolt xdomain; restrict/untrusted Thunderbolt device access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Thunderbolt xdomain subsystem)Systems with Thunderbolt ports/controllers
impact

Kernel use-after-free via Thunderbolt disconnect may cause crash, local privilege escalation, or kernel RCE if triggered by a malicious/untrusted device.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < d4fa0d544c04dea636bf821ff5582cd7d63e2c34
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < cfbd2dba3d862c9be8c92bea2a357d9ed828a54a
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < dc11d5118f9da6ea28487ffe055de5a0d0734125
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < 91b40862a02000f490b63f1d315be3ee31e83871
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < 33c0ee18cf8665c974b00f4e0ba769fbc07efe10
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < 54a62153c765cd24239cde1f2633f2a2fd005368
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < 2aa2cde2cc79a79d8ea4a15be9f4a67fc528ae91
  • affected>= 559c1e1e013437bf190469efbcbd8bc803285853 and < 2c5d2d3c3f70cde2565d7b279b544893a2035842
  • affected5.2
vendor says fixed in< 5.2, >= 5.10.266 and <= 5.10.*, >= 5.15.217 and <= 5.15.*, >= 6.1.184 and <= 6.1.*, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free