Answer in brief
CVE-2026-63893 records a Unknown severity vulnerability in thunderbolt: property: Reject u32 wrap in tb_property_entry_valid(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-63893 records a Unknown severity vulnerability in thunderbolt: property: Reject u32 wrap in tb_property_entry_valid(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <6a63623621639acbb39bc2d9fb09559681716695 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <9fee50c4e1e42f6d3cbe30df584f9f648f626071 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <8d4a758b407ab3de3be86d1ceadfa35d717d30c7 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <5c06a3043ad944f087bb2ae0aae28d820bb9f460 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <31b98e503ecca8077e5247253dd5425ab84bc96d || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <a47784aee77f33f786dc5d7375db821bdae68792 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <01deda0152066c6c955f0619114ea6afa070aaec | 6a63623621639acbb39bc2d9fb09559681716695, e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36, 9fee50c4e1e42f6d3cbe30df584f9f648f626071, 8d4a758b407ab3de3be86d1ceadfa35d717d30c7, 5c06a3043ad944f087bb2ae0aae28d820bb9f460, 31b98e503ecca8077e5247253dd5425ab84bc96d, a47784aee77f33f786dc5d7375db821bdae68792, 01deda0152066c6c955f0619114ea6afa070aaec |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid() entry->value is u32 and entry->length is u16; the sum is performed in u32 and wraps. A malicious XDomain peer can pick value = 0xffffff00, length = 0x100 so the sum 0x100000000 wraps to 0 and passes the > block_len check. tb_property_parse() then passes entry->value to parse_dwdata() as a dword offset into the property block, reading attacker-directed memory far past the allocation. For TEXT-typed entries with the "deviceid" or "vendorid" keys this lands in xd->device_name / xd->vendor_name and is readable back via the per-XDomain device_name / vendor_name sysfs attributes; the leak is NUL-bounded (kstrdup() stops at the first zero byte) and untargeted (the attacker picks a delta, not an absolute address). DATA-typed entries are parsed into property->value.data but not generically surfaced to userspace. Use check_add_overflow() so a wrapped sum is rejected.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <6a63623621639acbb39bc2d9fb09559681716695 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <9fee50c4e1e42f6d3cbe30df584f9f648f626071 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <8d4a758b407ab3de3be86d1ceadfa35d717d30c7 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <5c06a3043ad944f087bb2ae0aae28d820bb9f460 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <31b98e503ecca8077e5247253dd5425ab84bc96d || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <a47784aee77f33f786dc5d7375db821bdae68792 || >=cdae7c07e3e3509eaabc18c1640a55dc5b99c179 <01deda0152066c6c955f0619114ea6afa070aaec | 6a63623621639acbb39bc2d9fb09559681716695, e8a0b0a93a6ef958e70b1dd4930beb6dc0026b36, 9fee50c4e1e42f6d3cbe30df584f9f648f626071, 8d4a758b407ab3de3be86d1ceadfa35d717d30c7, 5c06a3043ad944f087bb2ae0aae28d820bb9f460, 31b98e503ecca8077e5247253dd5425ab84bc96d, a47784aee77f33f786dc5d7375db821bdae68792, 01deda0152066c6c955f0619114ea6afa070aaec |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid() entry->value is u32 and entry->length is u16; the sum is performed in u32 and wraps. A malicious XDomain peer can pick value = 0xffffff00, length = 0x100 so the sum 0x100000000 wraps to 0 and passes the > block_len check. tb_property_parse() then passes entry->value to parse_dwdata() as a dword offset into the property block, reading attacker-directed memory far past the allocation. For TEXT-typed entries with the "deviceid" or "vendorid" keys this lands in xd->device_name / xd->vendor_name and is readable back via the per-XDomain device_name / vendor_name sysfs attributes; the leak is NUL-bounded (kstrdup() stops at the first zero byte) and untargeted (the attacker picks a delta, not an absolute address). DATA-typed entries are parsed into property->value.data but not generically surfaced to userspace. Use check_add_overflow() so a wrapped sum is rejected.
Quoted source text, attributed separately from HOL analysis.