[CVE-2026-97509][LOW] thunderbolt: Keep XDomain reference during the lifetime of a service [ Upstream

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

CVE: CVE-2026-97509
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: thunderbolt: Keep XDomain reference during the lifetime of a service [ Upstream
Commit: a4567e5380e4e46d0ea9a28d2d675e5c6f013d54
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a4567e5380e4e46d0ea9a28d2d675e5c6f013d54
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97509
Analysis date: Thu, 24 Sep 2026 14:30:33 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-97509	LOW	https://www.kernelcve.org/list/?q=CVE-2026-97509 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';*CWE-416;*CWE-664;CWE-362;Other CVSS 'AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'A use after free can occur in the Thunderbolt XDomain service lifetime handling because a service may retain an XDomain pointer without holding a reference to the parent device. If the XDomain is removed before the service release callback runs, tb_service_release can access freed XDomain state while releasing the service ID. This may cause a kernel crash during Thunderbolt device removal or disconnect handling. For the CVSS the PR:N because an attacker does not need privileges on the host but needs physical access to a Thunderbolt device or connection path. The issue is not network reachable. Impact is at least denial of service. The use after free may also have limited confidentiality or integrity impact in a worst case memory reuse scenario and should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	YES	HARDWARE DEBUGFS 	NO	NO	checked

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

ActionableScore=2
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 2
* Conservative score: 2
* Raw paranoid score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +2 Real UAF or lifetime violation. `tb_service_release()` accesses `xd->service_ids` through the XDomain parent relationship, but the service did not hold a device reference keeping the XDomain alive. The XDomain can therefore be freed before service release.
* +1 Firmware or device mediated external influence. A connected Thunderbolt peer device and its disconnect or removal lifecycle materially participate in reaching the vulnerable teardown sequence.
* +1 Plausible kernel crash or strong DoS. Calling `ida_free()` through a stale XDomain object can dereference freed kernel memory and cause an Oops or kernel crash.
* -2 Physical access requirement. Triggering requires access to a Thunderbolt device or connection path. This is a physical peripheral lifecycle issue, not directly network reachable.

Not awarded:

* Controlled reclaim or attacker controlled replacement of the freed XDomain object is not demonstrated.
* Arbitrary or directed kernel write is not demonstrated.
* Structured stale object leverage is not awarded. Although `struct tb_xdomain` is an active structured object, the visible stale use is limited to the service release cleanup path and `ida_free()`.
* Concrete repeated release or refcount mutation is not established. `get_device()` and `tb_xdomain_put()` form the intended matching reference pair introduced by the fix. The vulnerable pre-fix path is a stale parent object dereference, not a second put on the same dangling reference.
* Confidentiality and integrity impact are not awarded. A theoretical reclaimed-memory scenario is insufficient without a demonstrated disclosure, controlled reuse, write primitive, callback consumption, or security-boundary consequence.
* Remote reachability is not established.
* No paranoid bonus is awarded. The patch establishes a real UAF, but does not establish a stronger post-free primitive beyond the cleanup-time stale dereference.

3. Reachability analysis

The relevant attacker model is a person or device with physical access to a Thunderbolt port, cable, or connected Thunderbolt peer. The XDomain service lifecycle is associated with enumeration and removal of a Thunderbolt domain or service, so a disconnect or malicious-device lifecycle can plausibly exercise the affected teardown path.

The supplied patch does not establish whether a fully unprivileged local user can independently create the required XDomain and service state without a physical Thunderbolt device. It also does not establish that host administrator privileges are required for the complete trigger. Therefore `HostAdminRequired=UNKNOWN`.

No network namespace, user namespace, or namespace-scoped capability path is shown. `NamespaceScopedPrivilege=UNKNOWN`.

A Thunderbolt-capable host and physical Thunderbolt access are material prerequisites. The issue is not directly network reachable and should not be treated as a remotely triggerable networking vulnerability. The supplied evidence does not establish a narrow timing race. The bug is primarily an ownership and lifetime mismatch during device or service teardown.

4. Primitive and severity interpretation

The exact primitive is a real lifetime violation. A Thunderbolt service can outlive the XDomain device object that owns `service_ids`, while `tb_service_release()` still accesses that XDomain state through the service parent relationship.

This is an active structured-object UAF, but the demonstrated stale use is cleanup and destructor oriented. The visible post-lifetime operation is `ida_free(&xd->service_ids, svc->id)`. It consumes a field of the freed XDomain object but does not, from the supplied evidence, provide attacker-controlled replacement contents, callback dispatch, controlled refcount takeover, arbitrary read, arbitrary write, or a security-boundary bypass.

This is `CLASS_B`, not `CLASS_A`. The demonstrated practical consequence is kernel crash or denial of service during Thunderbolt removal or disconnect handling. Limited confidentiality or integrity effects remain theoretical and are not counted because the patch does not establish meaningful reuse or post-free control.

`ImportantCandidate=NO` because this is a constrained cleanup-time UAF with physical-device prerequisites and no demonstrated exploitation leverage beyond the stale-object dereference. `AutoDowngradeAllowed=YES` because no concrete repeated lifetime mutation, controlled reclaim, boundary bypass, or unresolved strong active-object reuse mechanism is established. Manual review remains recommended because the issue is a genuine kernel lifetime UAF, even though the available evidence supports ordinary Moderate operational handling.

5. One-sentence report phrase

A Thunderbolt XDomain lifetime bug can cause `tb_service_release()` to access freed XDomain service ID state after device removal, allowing a physically connected Thunderbolt device or disconnect sequence to trigger a kernel crash and denial of service.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

The patch establishes a real UAF in a driver teardown path, but the currently available evidence supports a physically triggered crash scenario rather than controlled post-free exploitation.

7. Call-site confidence

Call-site confidence: medium

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

Patch: thunderbolt: Keep XDomain reference during the lifetime of a service [ Upstream
Commit: a4567e5380e4e46d0ea9a28d2d675e5c6f013d54
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a4567e5380e4e46d0ea9a28d2d675e5c6f013d54

Changed files:
  drivers/thunderbolt/xdomain.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=a4567e5380e4e46d0ea9a28d2d675e5c6f013d54

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

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

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

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: unknown
  Paranoid ActionableScore: 2

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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