[CVE-2026-63892][MODERATE REGULAR] thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow

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

CVE: CVE-2026-63892
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow
Commit: 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=37abc4504fa19d8f9f1e87792e8a2b8fdb308e40
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-63892
Analysis date: Sun, 19 Jul 2026 17:14:47 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
A malformed Thunderbolt or USB4 XDomain property directory with dir_len below 4 can trigger an OOB read and size_t underflow in the kernel property parser, leading primarily to a device-mediated kernel crash with limited paranoid concern for additional memory-safety impact.

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

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

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-63892	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H';CWE-125;CWE-191;*CWE-20;Other CVSS 'AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.7';DESCR 'A Thunderbolt property directory parsing bug can occur when a non root directory entry advertises dir_len below 4. The parser may copy a fixed size UUID from near the end of the property block and then compute content_len as dir_len minus 4, causing size_t underflow and an oversized entry walk. This can lead to out of bounds kernel reads and a kernel crash when a crafted Thunderbolt or USB4 peer device supplies malformed XDomain property data. For the CVSS the PR:N because the attacker does not need a local account on the target, but must be able to connect or control the relevant Thunderbolt or USB4 peer device. The issue is not Internet reachable and is best modeled as physical access to a peripheral path. Impact is at least denial of service. For the paranoid score, limited confidentiality or integrity impact is kept because the primitive is OOB read and parser state confusion, but no direct OOB write or arbitrary write primitive is evident.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3)  SKIP CVE-2026-63892 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	OOB INIT IMPROVEONLY  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 recommended**

## 2. Signal breakdown

Triggered signals:

* Firmware-mediated external influence: +1
  Malformed Thunderbolt or USB4 XDomain property data can be supplied by an external peer device or device-side firmware path.

* Memory corruption, weak or indirect corruption candidate: +1
  The primitive is an OOB read plus size_t underflow leading to an oversized parser walk. No OOB write, UAF, double free, arbitrary write, or type confusion is shown.

* Reliable kernel crash / strong DoS: +1
  The commit explicitly describes OOB walking until validation fails or the kernel oopses on an unmapped page.

* Privileged kernel/device-management memory corruption path: +1
  The bug is in a trusted Thunderbolt kernel parser for device supplied property data.

Paranoid-only signals:

* Confidentiality impact plausible: +1
  Limited OOB read exists, but no concrete user-visible disclosure path is demonstrated.

* Integrity impact plausible: +1
  Parser state confusion is possible after size_t underflow, but no write primitive is shown, so this remains weak.

Negative signals:

* Physical-only or rare hardware-only condition: -2
  Triggering requires control of or connection to a Thunderbolt or USB4 peer path, not ordinary remote network reachability.

* Corruption primitive highly constrained or read-only: -1
  The demonstrated primitive is read-side OOB traversal and crash, not attacker-controlled overwrite.

Conservative arithmetic: +1 +1 +1 +1 -2 -1 = 1, rounded up to 2 due to explicit kernel OOB read in a device parser.
Paranoid arithmetic: conservative 2 + confidentiality concern 1 + integrity concern 1 = 4.

Call-site confidence: high. The vulnerable parser path and the direct consequences of dir_len below 4 are described in the commit and visible in the provided diff.

## 3. Reachability analysis

The likely attacker is someone who can connect, emulate, or control a Thunderbolt or USB4 peer device that provides malformed XDomain property data. No local Linux account is required, so this is not PR:L in a local-user sense, but it is also not Internet-reachable. Namespaces and containers do not materially lower the requirement because the trigger is outside normal process APIs and depends on the physical or device-management path.

The affected code is relevant only on systems with Thunderbolt or USB4 support and the corresponding property parsing path. This is common on some laptops and workstations but not a broad default server exposure. Realistic exploitation conditions require proximity or control over a connected device path.

## 4. Severity interpretation

This behaves more like a Borderline / actionable Moderate issue than an Important-class vulnerability. The patch demonstrates a real kernel memory-safety problem: OOB read and integer underflow in a trusted parser, with plausible kernel crash. However, realistic exploitation is limited by physical or device-mediated reachability, and the patch does not show OOB write, UAF reclaim, arbitrary write, callback control, or a clear LPE path.

The theoretical worst case includes limited confidentiality or integrity concern because an oversized parser walk can interpret memory outside the intended property block. The realistic evidence supports DoS much more strongly than privilege escalation.

## 5. One-sentence report phrase

A malformed Thunderbolt or USB4 XDomain property directory with dir_len below 4 can trigger an OOB read and size_t underflow in the kernel property parser, leading primarily to a device-mediated kernel crash with limited paranoid concern for additional memory-safety impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is an externally influenced kernel parser bug with explicit OOB read and size_t underflow. It is probably not Important by default because the reachability is physical/device-mediated and no write primitive is shown, but the memory-safety nature makes auto-close unsafe without manual confirmation.

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

Patch: thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow
Commit: 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=37abc4504fa19d8f9f1e87792e8a2b8fdb308e40

Commit description:

On the non-root path, __tb_property_parse_dir() takes dir_len from
entry->length (u16 widened to size_t).  Two distinct OOB conditions
follow when entry->length < 4:

1. The non-root path begins with kmemdup(&block[dir_offset],
   sizeof(*dir->uuid), ...) which always reads 4 dwords from
   dir_offset.  tb_property_entry_valid() only enforces
   dir_offset + entry->length <= block_len, so a crafted entry
   with dir_offset close to the end of the property block and
   entry->length in 0..3 passes that gate but lets the UUID copy
   run off the block (e.g. dir_offset = 497, dir_len = 3 in a
   500-dword block reads block[497..501]).

2. After the kmemdup, content_len = dir_len - 4 underflows size_t
   to ~SIZE_MAX, nentries becomes SIZE_MAX / 4, and the entry
   walk runs OOB on each iteration until an entry fails
   validation or the kernel oopses on an unmapped page.

Reject dir_len < 4 on the non-root path *before* the UUID kmemdup,
which closes both holes.

Also move INIT_LIST_HEAD(&dir->properties) up to immediately after
the dir allocation so the new error-return path (and the existing
uuid-alloc failure path) calling tb_property_free_dir() sees a
walkable list rather than the zero-initialized NULL next/prev that
list_for_each_entry_safe() would oops on.

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=37abc4504fa19d8f9f1e87792e8a2b8fdb308e40

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

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

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:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 5.7

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).