Skip to content
Systems

CVE-2026-63893

HIGH
High
EPSS 0.39%Patch availableJul 21, 2026

Linux kernel Thunderbolt parsing bug leaks kernel memory via crafted XDomain properties.

common questions

Is CVE-2026-63893 being exploited?

Not confirmed. CVE-2026-63893 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.39% probability of exploitation in the next 30 days.

How severe is CVE-2026-63893?

CVE-2026-63893 is rated High. 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-63893?

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

What does CVE-2026-63893 affect?

CVE-2026-63893 affects Linux kernel (thunderbolt module), Systems using Thunderbolt XDomain/XDP interfaces. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63893?

Apply vendor/linux kernel security update promptly; restrict Thunderbolt 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 module)Systems using Thunderbolt XDomain/XDP interfaces
impact

Local or device-attached attacker can read kernel memory via crafted Thunderbolt XDomain properties; sensitive data may be exfiltrated via sysfs attributes.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 6a63623621639acbb39bc2d9fb09559681716695
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 9fee50c4e1e42f6d3cbe30df584f9f648f626071
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 8d4a758b407ab3de3be86d1ceadfa35d717d30c7
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 5c06a3043ad944f087bb2ae0aae28d820bb9f460
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 31b98e503ecca8077e5247253dd5425ab84bc96d
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < a47784aee77f33f786dc5d7375db821bdae68792
  • affected>= cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and < 01deda0152066c6c955f0619114ea6afa070aaec
  • affected4.15
vendor says fixed in< 4.15, >= 5.10.259 and <= 5.10.*, >= 5.15.210 and <= 5.15.*, >= 6.1.176 and <= 6.1.*, >= 6.6.143 and <= 6.6.*, >= 6.12.93 and <= 6.12.*, >= 6.18.35 and <= 6.18.*, >= 7.0.12 and <= 7.0.*, >= 7.1 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