[CVE-2026-98689][MODERATE REGULAR] thunderbolt: Don't access a DP tunnel after its DPRX read was canceled [ Upstream

[CVE-2026-98689][MODERATE REGULAR] thunderbolt: Don't access a DP tunnel after its DPRX read was canceled [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98689
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: thunderbolt: Don't access a DP tunnel after its DPRX read was canceled [ Upstream
Commit: 405a969c0b3356639116db89ab367be1d64b77c0
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=405a969c0b3356639116db89ab367be1d64b77c0
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98689
Analysis date: Mon, 19 Oct 2026 06:24:54 -0400
ActionableScore: 4
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
A race between DPRX work cancellation and Thunderbolt DisplayPort tunnel teardown can make the callback access adapters after their routers have gone away, creating a constrained stale-object or UAF risk with a plausible local kernel crash.

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

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

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-98689	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98689 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-362;*CWE-416;*CWE-672;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race in Thunderbolt DisplayPort tunnel handling allows tb_dp_dprx_work to pass the cancellation check before taking tb lock and then continue after the DPRX operation has been canceled. During suspend or domain teardown the work can poll DPRX capabilities and invoke the activation callback for a tunnel whose adapters or routers may already be going away. The tunnel object itself appears to remain referenced until tb_tunnel_put, but the lifetime of associated adapters and routers creates a plausible stale access or UAF risk that requires source level verification. For the CVSS the PR:L value is used because a local user or constrained service may be able to request system suspend or trigger an authorized Thunderbolt management operation without full administrative control. AC:H applies because exploitation depends on winning the race between asynchronous DPRX work and tunnel teardown. The issue is not network reachable and requires affected Thunderbolt or USB4 DisplayPort tunnel hardware. Impact is at least a local denial of service via a kernel crash and in the paranoid interpretation may include confidentiality or integrity impact if the stale adapter or router access is confirmed as exploitable memory corruption. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 7 and the production ActionableScore returned 4 with recommendation Borderline / manual review recommended. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage LOW to MODERATE_KPANIC because the ActionableScore threshold rule was applied. KP and FD specialist checks stage MODERATE_KPANIC to MODERATE because KP specialist did not establish a qualifying panic. The legacy KP specialist produced a review artifact and its decision was processed by the applicable KP rules. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 and DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 2.0 and ActionableScore 1 with primitive class CLASS_C and manual review RECOMMENDED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 4)	MAYBE	READ LOCK IMPROVEONLY LINUS  INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED	-	-	checked

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

ActionableScore=4
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

## 1. ActionableScore

* Raw conservative score: 2
* Conservative score: 4
* Raw paranoid score: 2
* Paranoid score: 4
* Applied conservative floor: 2 -> 4 under the Real UAF floor because post-teardown structured objects are accessed and host-admin privilege is not established.
* Applied paranoid floor: 2 -> 4 for the same reason.
* Final recommended bucket: **Borderline / manual review recommended**::

## 2. Signal breakdown

* +2 Real UAF or lifetime violation. The canceled DPRX work can continue after tunnel teardown and access adapters whose routers may already be gone.
* No crash point awarded. A kernel fault is plausible, but the supplied evidence does not demonstrate an Oops or panic.
* No structured stale-object leverage awarded. The callback performs active processing, but attacker-controlled reclaim, replacement contents, pointers, offsets, callbacks, or refcounts are not established.
* No repeated release or refcount point awarded. `tb_tunnel_put()` is shown once, and the patch does not establish a second lifetime mutation through the same dangling reference.
* No timing penalty applied. Although this is a race, the incomplete DPRX read can leave a substantial cancellation window, and the commit documents an observed occurrence.
* No hardware penalty applied. Thunderbolt or USB4 DisplayPort tunneling is required, but the evidence does not establish physical attacker access or sufficiently rare hardware.
* No remote, namespace, authorization, confidentiality, integrity, or privilege-escalation points awarded.
* B5-R does not apply. There is no retry-accumulated heap OOB write.
* B3-PENDING does not apply. There is no shared-backing write.
* B4-PENDING does not apply. No authorization decision changes from DENY to ALLOW.
* NEW52, NEW53, V32, V33, and V34 do not apply because the patch does not involve an OOB write, skb checksum metadata, or cross-boundary metadata consumption.

## 3. Reachability analysis

The vulnerable sequence occurs when asynchronous DPRX work overlaps cancellation and tunnel teardown during suspend or Thunderbolt domain shutdown. Affected Thunderbolt or USB4 DisplayPort tunnel hardware and an in-flight DPRX operation are prerequisites.

The commit confirms that suspend and `tb_stop()` can reach the cancellation path, but it does not establish whether an ordinary logged-in user, compositor, delegated hardware-management service, or only a host administrator can complete the trigger. Therefore, `HostAdminRequired=UNKNOWN` and `RequiresHostUID0=UNKNOWN`.

No user-namespace or network-namespace capability path is involved, so `NamespaceScopedPrivilege=NO`. The issue is not remotely network-triggerable. The race was observed with Apple NHI where the DPRX read did not complete, which makes the vulnerable ordering credible but does not establish reliable attacker control.

## 4. Primitive and severity interpretation

The exact primitive is asynchronous post-teardown access to active structured Thunderbolt state. The `tb_tunnel` object itself appears to remain referenced until `tb_tunnel_put()`, but its associated adapters and routers may have completed teardown before the DPRX callback accesses them. This directly implies a stale-object or UAF-class lifetime violation for associated objects.

This is broader than a fixed stale transfer buffer because the callback inspects and updates active tunnel and adapter state. However, it remains closely tied to suspend or domain teardown. There is no demonstrated controlled reclaim, replacement object, stale callback dispatch from reclaimed memory, arbitrary read or write, repeated refcount mutation, disclosure, or security-boundary bypass.

The patch-supported consequence is unsafe post-teardown access with a plausible kernel crash. Privilege escalation and confidentiality or integrity impact remain speculative and are not scored. Consequently, this is constrained `CLASS_B`, not `CLASS_A`.

`ImportantCandidate=NO` because meaningful exploitation leverage beyond stale access and possible DoS is not established. `AutoDowngradeAllowed=YES` because the available evidence supports a constrained teardown UAF without controlled reuse or an unresolved cross-boundary primitive. Manual review is still recommended to verify the exact lifetimes of `src_port`, adapters, routers, and switch objects.

## 5. One-sentence report phrase

A race between DPRX work cancellation and Thunderbolt DisplayPort tunnel teardown can make the callback access adapters after their routers have gone away, creating a constrained stale-object or UAF risk with a plausible local kernel crash.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Confirm whether adapter or router storage can be freed before `tb_dp_tunnel_active()` runs and whether any stale field access occurs before an immediate fault or can consume reused structured state.

## 7. Call-site confidence

Call-site confidence: high

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

Patch: thunderbolt: Don't access a DP tunnel after its DPRX read was canceled [ Upstream
Commit: 405a969c0b3356639116db89ab367be1d64b77c0
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=405a969c0b3356639116db89ab367be1d64b77c0

Changed files:
  drivers/thunderbolt/tb.c
  drivers/thunderbolt/tunnel.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=405a969c0b3356639116db89ab367be1d64b77c0

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

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

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