CVE-2026-97509

Description

A flaw was found in the Linux kernel's Thunderbolt subsystem. A local attacker could exploit this issue to cause a Denial of Service (DoS) or potentially execute arbitrary code. The vulnerability occurs because the driver fails to maintain a reference to the parent domain device during the lifetime of an active service, allowing the parent structure to be deallocated prematurely. When the service is later destroyed, accessing the released structure results in a use-after-free condition that crashes the system.

Statement

A low impact use-after-free flaw was found in the Linux kernel's Thunderbolt subsystem. The driver did not keep a reference to the parent XDomain device during the lifetime of an enumerated service, so if the XDomain was deallocated before the service was destroyed (for example when a Thunderbolt/USB4 device is disconnected), tb_service_release() accessed the already freed parent structure when releasing the service ID, resulting in a use-after-free that can crash the kernel (denial of service) and potentially allow arbitrary code execution. Red Hat Enterprise Linux 7 (including kernel-rt), 8, 9, and 10, Red Hat In-Vehicle OS 2, and the RHEL CoreOS content shipped with OpenShift Container Platform 4 and 5 are affected; Red Hat Enterprise Linux 6 is not affected because the vulnerable code is not present in that release.

Exploitation requires local access to a system with Thunderbolt hardware and depends on the timing of device removal, and the issue is not network reachable. Red Hat therefore rates the impact as low (Red Hat CVSS 5.5, Moderate), which differs significantly from the upstream CVEORG severity of 8.8 (Important). Fixes for the affected products are deferred given the low impact and the local, hardware-dependent access required to trigger the flaw; the residual risk is primarily a local denial of service (system crash), with code execution theoretically possible but not demonstrated.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A8.8
Attack VectorLocalN/AAdjacent Network
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.