[CVE-2026-63893][MODERATE REGULAR] thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-63893
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()
Commit: 6a63623621639acbb39bc2d9fb09559681716695
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6a63623621639acbb39bc2d9fb09559681716695
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63893
Analysis date: Sun, 19 Jul 2026 13:30:06 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline manual review required / Not auto-close
Manual review required: YES

Summary:
A malicious Thunderbolt XDomain peer can exploit a u32 wrap in property validation to trigger an out-of-bounds kernel read and expose limited kernel memory through XDomain device_name or vendor_name sysfs attributes.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63893 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63893

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-63893	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N';CWE-190;CWE-125;*CWE-200;Other CVSS 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N';BEST CVSS score: '6.5';DESCR 'A u32 integer wrap in Thunderbolt XDomain property validation can allow an attacker controlled property entry to pass bounds checks with a wrapped end offset. The parser may then read from an out of bounds dword offset beyond the allocated property block and copy TEXT values into device_name or vendor_name fields that can later be read through sysfs. For the CVSS the PR:N because the attacker does not need a local account on the victim, but does need the ability to act as a malicious Thunderbolt XDomain peer. The issue is not reachable over the public Internet and normally requires physical or adjacent access to a Thunderbolt or USB4 fabric where XDomain property exchange is enabled. Impact is information disclosure. No write primitive or direct privilege escalation path is shown by the patch context.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review required / Not auto-close (with actual score 3)  SKIP CVE-2026-63893 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	SIMPLEFIX LEAK HARDWARE  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review required / Not auto-close**::

## 2. Signal breakdown

* Firmware-mediated or external device influence: +1. A malicious Thunderbolt XDomain peer can provide attacker-controlled property entries.
* Attacker-directed OOB kernel read with disclosure path: +1. The wrapped value plus length check can allow parse_dwdata() to read beyond the allocated property block.
* Confidentiality impact plausible: +1. TEXT entries for deviceid or vendorid can be copied into device_name or vendor_name and exposed through sysfs.
* Practical disclosure path strongly implied: +1. The commit describes a concrete path from malformed XDomain property to sysfs-readable fields.
* Privileged device-management parser context: +1 in paranoid scoring. The bug is in a trusted Thunderbolt property parser fed by an external peer.
* Constrained disclosure: -1. The leak is NUL-bounded and untargeted, with attacker control over an offset delta but not an absolute address.
* Physical or adjacent hardware exposure: -2 in the conservative score. Realistic triggering normally requires a malicious Thunderbolt or USB4 XDomain peer, not Internet reachability.

## 3. Reachability analysis

The attacker does not need a local Linux account on the victim, so PR:N is reasonable for CVSS-style privilege interpretation. The attacker does need the ability to act as a malicious Thunderbolt or USB4 XDomain peer, which is closer to physical or adjacent-device exposure than normal remote network exposure. This is not reachable over the public Internet. Namespaces and containers do not materially lower the requirement because the input comes from Thunderbolt XDomain property exchange, not a local userspace API.

Call-site confidence: high. The commit message gives the relevant validation failure, parser consequence, and sysfs read-back path.

## 4. Severity interpretation

This behaves like an actionable information disclosure issue, not a generic DoS and not a demonstrated privilege-escalation bug. The primitive is an attacker-directed out-of-bounds kernel read with a user-visible disclosure path, but it is constrained because the leak is NUL-bounded and untargeted. There is no supported write primitive, type confusion, UAF, or direct LPE path in the patch context. The issue should not be treated as Important by default, but it should not be auto-closed because kernel memory disclosure from an external Thunderbolt peer is security-relevant.

## 5. One-sentence report phrase

A malicious Thunderbolt XDomain peer can exploit a u32 wrap in property validation to trigger an out-of-bounds kernel read and expose limited kernel memory through XDomain device_name or vendor_name sysfs attributes.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the issue has a concrete attacker-directed OOB kernel read and a sysfs-readable disclosure path, even though exposure is physical or adjacent and the leak is constrained.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()
Commit: 6a63623621639acbb39bc2d9fb09559681716695
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6a63623621639acbb39bc2d9fb09559681716695

Commit description:

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.

Fixes: cdae7c0 ("thunderbolt: Add support for XDomain properties")
Cc: stable@vger.kernel.org
Assisted-by: Claude:claude-opus-4-6
Assisted-by: Codex:gpt-5-4
Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/thunderbolt/property.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6a63623621639acbb39bc2d9fb09559681716695

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-63893 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63893

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
  The Best / paranoid CVSS vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  The Best / paranoid CVSS score: 6.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 2
  Paranoid ActionableScore: 4

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).