PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-63891 Linux CVE debrief

The Linux kernel was vulnerable to a stack exhaustion issue in the thunderbolt property parsing logic. A crafted peer could trigger this without authentication by chaining DIRECTORY entries into a back-reference loop. This vulnerability affects systems with untrusted XDomain peers connected via Thunderbolt, such as hosts, docks, or inline inspectors. Operators of such systems should take immediate action to mitigate the vulnerability.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-19
Original CVE updated
2026-07-19
Advisory published
2026-07-19
Advisory updated
2026-07-19

Who should care

Operators of systems with untrusted XDomain peers connected via Thunderbolt, such as hosts, docks, or inline inspectors, should be aware of this vulnerability and take necessary precautions. This includes restricting access to Thunderbolt ports to trusted peers only and monitoring for unusual Thunderbolt activity.

Technical summary

The Linux kernel's thunderbolt property parsing logic did not cap recursion depth, leading to a potential stack exhaustion vulnerability. A malicious peer could exploit this by creating a loop of DIRECTORY entries, causing the parser to recurse until the kernel stack is exhausted. This vulnerability can be triggered without authentication by any untrusted XDomain peer that reaches the PROPERTIES_REQUEST control-plane exchange.

Defensive priority

High

Recommended defensive actions

  • Disable the Thunderbolt XDomain path entirely with thunderbolt.xdomain=0 on the kernel command line if not needed.
  • Restrict access to Thunderbolt ports to trusted peers only.
  • Monitor for unusual Thunderbolt activity and implement exception tracking.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record was published on 2026-07-19T16:17:06.440Z and has not been modified since then. The NVD entry is currently Received. There is no additional information available about the vulnerability beyond what is provided in the CVE record and NVD entry.

Official resources

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-19T16:17:06.440Z and has not been modified since then.