CVE-2026-63891

thunderbolt: property: Cap recursion depth in __tb_property_parse_dir()

N/A
Published: July 19, 2026 at 02:55 PM UTC
Updated: July 27, 2026 at 05:57 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.3%

Description

In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() A DIRECTORY entry's value field is used as the dir_offset for a recursive call into __tb_property_parse_dir() with no depth counter. A crafted peer that chains DIRECTORY entries into a back-reference loop drives the parser until the kernel stack is exhausted and the guard page fires. Any untrusted XDomain peer (cable, dock, in-line inspector, adjacent host) that reaches the PROPERTIES_REQUEST control-plane exchange can trigger this without authentication. Thread a depth counter through tb_property_parse() and __tb_property_parse_dir(), and reject blocks that exceed TB_PROPERTY_MAX_DEPTH = 8. That is comfortably larger than any observed legitimate XDomain layout. Operators who do not need XDomain host-to-host discovery can disable the path entirely with thunderbolt.xdomain=0 on the kernel command line.

Affected

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

4.15 ≤ v < 5.10.2594.15 ≤ v < 5.15.2104.15 ≤ v < 6.1.1764.15 ≤ v < 6.12.934.15 ≤ v < 6.18.354.15 ≤ v < 6.6.1434.15 ≤ v < 7.0.124.15 ≤ v < 7.14.15cdae7c07e3e3509eaabc18c1640a55dc5b99c179
Vendor states this is fixed in 0a84ab9271936c11e84e511bb52fc5682f8b6726 (fixed)
Vendor states this is fixed in 2b5f47a710172c962ef42d1b732b04d2ad0dce21 (fixed)
Vendor states this is fixed in 830c8a9b467e7d3a158483d37fa7dc13892b293a (fixed)
Vendor states this is fixed in 928abe19fbf0127003abcb1ea69cabc1c897d0ab (fixed)
Vendor states this is fixed in 95839a67ea56ca35732aad7f711404a3127cfe2d (fixed)
Vendor states this is fixed in b4621e5ef63405c317a84b711faf3bd75b3c6a94 (fixed)
Vendor states this is fixed in ed9455ef4bd9babc90f92e526abe3fb68c1a8709 (fixed)
Vendor states this is fixed in f31c6d220f455b5af63590302b30e1b932d14599 (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (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

StatusAWAITING ANALYSIS

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